-
Notifications
You must be signed in to change notification settings - Fork 793
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
Extension for property initializers #17
Conversation
match styling change. added open module to remove fully qualified path removed unnecessary comment "//need to hide" added during prototyping
Great! I've updated the link on the status page to point to this one |
I still need to fix the build. |
@forki I've checked it - it is fine. |
Thanks for taking this and getting it in shape. Looks good to me, issues all seem to be resolved now. I will merge it in a minute, hopefully I have the comment right so that it closes properly here. |
Thanks, this is great, it looks good, although regrettably I'm having system setup issues at the moment so I can't see it running. |
fix bug where unfold did not respect the Halted state on Result
Bind only from XAML
This implements support for extension properties setters in initializers as described UserVoice: http://fslang.uservoice.com/forums/245727-f-language/suggestions/6200089-allow-extension-properties-setters-in-initializers
It was originally submited by Edward Paul (@xepaul) at https://visualfsharp.codeplex.com/SourceControl/network/forks/EdwardPaul/PropertyInitializationExperiments/contribution/7391
As the deadline is tomorrow I wanted to step in and rebased this on current fsharp4 branch