-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to create generative providers with the new context based provided type API without error. #82
Comments
@dsyme Any advice on getting this to work on generative would be greatly received :-) |
@7sharp9 Can you give a detailed repro for this please, with a link to a sample project or PR, and details of operating system etc.? |
I don't currently have a public repro but Ill see about making one. |
Ok, repro repo is here: This code used to work fine before using the ctxt to add the various provided entities. I used the very lasted code that was committed here this morning. |
@7sharp9 Could you please add this as a test to this repo? |
@sergey-tihon Thats the thing, it doesn't work at all yet for generatives. |
Ok this has been here for a year now, is the context API going to be the way forward or forever experimental? //cc @dsyme |
@7sharp9 @dsyme I debugged the repro what I found is that when using types like then this type is converted using this function: when I changed the implementation of replaceType to return the same type for types defined in mscorlib then I tried to understand why this convert is needed for types that is not provided types still didn't understand why it's needed I tried also to make the base type of the provider a type that i decleared in the ContextBasedGenerative this is the summary for what I found till now |
I've added a comment about this here #133 (comment) I think we need to move to a different IL writer for generative providers authored using this SDK - that is needed for .NET Core/.NET Standard in any case. I'm quite keen to minimize binary dependencies, so I'm inclined to use the Abstract IL writer from the F# compiler, since it can be just a single file (like our assembly reader), but I need to think about it. |
@AviAvni Thanks, this is fixed through the updated SDK |
Currently if I convert to the new API I get a:
Which seems to stem from assembly generator:
If would be great if the provided types API was able to support unchecked quotation for generative types as they have the same issues relating to reflection based loading etc.
The text was updated successfully, but these errors were encountered: