Fix docs about "LLVM Marshal Methods" #2566
Conversation
It appears this section might have been AI generated, as it appeared to contain "hallucinated" MSBuild property names. It also didn't make sense that the example set things to `false`. I updated the section as appropriate. We also have made the feature non-default in: * dotnet/android#9336 I also linked to GitHub commits, as we have more detailed text inside, generally, than pull requests.
|
|
||
| ```xml | ||
| <PropertyGroup Condition="'$(TargetFramework)' == 'net9.0-android'"> |
There was a problem hiding this comment.
There is no need to put Condition in the example as $(AndroidEnableMarshalMethods) will have no affect on other platforms.
|
@jonathanpeppers It wasn't AI generated (AI generated content requires a legal disclaimer) - it was PM generated (see https://github.com/dotnet/core/blob/main/release-notes/9.0/preview/preview5/dotnetmaui.md#llvm-marshalled-methods). |
It's weird, the "made up" property names aren't in our repo at all: The simplest explanation (maybe?) is someone took all the release notes and fed them through an LLM, which would happily invent plausible MSBuild property names. |
It appears this section might have been AI generated, as it appeared to contain "hallucinated" MSBuild property names. It also didn't make sense that the example set things to
false. I updated the section as appropriate.We also have made the feature non-default in:
I also linked to GitHub commits, as we have more detailed text inside, generally, than pull requests.
Internal previews