Skip to content
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

Closed
KevinRansom opened this issue Jan 25, 2015 · 0 comments
Labels

Comments

@KevinRansom
Copy link
Member

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

2nhackv
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:

  • Omitting the optional parameter
  • Including the optional parameter, when the value matches the specified default

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:

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
@latkin latkin closed this as completed in f46558c Feb 5, 2015
@latkin latkin added the fixed label Feb 5, 2015
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants