[Draft] Don't include PhantomData fields in IdlBuild impl

[ssadler]

Hi, I made this small change which addresses #3241 in order to be able to use a PhantomData field in an account.

It gets the IDL to build by filtering out PhantomData fields, however i have not tested it the other way, i.e., what happens if you want to encode a struct that includes a PhantomData field from a JS input.

Would like to know if this PR is acceptable as is, or what other changes need to be made also? For example:

• Test that IDL definition does not include PhantomData fields
• Signed Git commit
• Some comments would be nice

Best

[vercel]

@ssadler is attempting to deploy a commit to the coral-xyz Team on Vercel.

A member of the Team first needs to authorize it.

[acheroncrypto]

Thanks for taking the time to work on this!

I think we also need to remove the generics that are only used by the PhantomData to make the definition valid. Otherwise, using declare_program! with this IDL would result in a compile error because Rust doesn't allow unused generic parameters.

Would like to know if this PR is acceptable as is, or what other changes need to be made also?

It's helpful and has minimal changes, so yes, it's certainly acceptable. However, it would be great to have some tests for this in here. Tests should cover compilation of a definition with:

• Existing generic parameters (other than the one used by the PhantomData field)
• No existing generic parameters

The generated IDL should also be checked to make sure:

• The PhantomData fields don't exist
• Generic parameter definitions are correctly omitted.

[acheroncrypto]

Nit: match arms more or less follow the order of IdlType, so it would be great if you could move this logic either inside the Defined impl:

anchor/lang/syn/src/idl/defined.rs

Lines 484 to 485 in 6df05aa

	// Defined
	syn::Type::Path(path) => {

or just above it.

[ssadler]

I think we also need to remove the generics that are only used by the PhantomData to make the definition valid. Otherwise, using declare_program! with this IDL would result in a compile error because Rust doesn't allow unused generic parameters.

How would I produce this error? The change is Works On My Machine(TM), because though the account struct has a generic param, it's only the impl that omits encoding the PhantomData field and rust allows that. Updated title.