-
Notifications
You must be signed in to change notification settings - Fork 802
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Using a single, optional, static parameter to a type provider causes failure #98
Labels
Comments
forki
added a commit
to forki/visualfsharp
that referenced
this issue
Jan 25, 2015
forki
added a commit
to forki/visualfsharp
that referenced
this issue
Jan 25, 2015
forki
added a commit
to forki/visualfsharp
that referenced
this issue
Jan 30, 2015
forki
added a commit
to forki/visualfsharp
that referenced
this issue
Jan 30, 2015
forki
added a commit
to forki/visualfsharp
that referenced
this issue
Feb 3, 2015
forki
added a commit
to forki/visualfsharp
that referenced
this issue
Feb 3, 2015
forki
added a commit
to forki/visualfsharp
that referenced
this issue
Feb 4, 2015
forki
added a commit
to forki/visualfsharp
that referenced
this issue
Feb 4, 2015
forki
added a commit
to forki/visualfsharp
that referenced
this issue
Feb 4, 2015
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Originally opened on CodePlex by [latkin](Using a single, optional, static parameter to a type provider causes failure)
[originally reported to fsbugs]
Repro solution attached
If one creates a type provider with a single, optional, static parameter (i.e. single parameter with a default value specified), two scenarios are broken:
E.g. TP "Test" has single string optional arg, with default value "Foo":
Image
Fix strategy, per Vlad:
"Fix seems to be trivial - one line addition in name demangling routine (demangleProvidedTypeName in PrettyNaming.fs)"
Repro:
The text was updated successfully, but these errors were encountered: