Described here
https://stackoverflow.com/questions/8154730/object-expression-for-abstract-class-without-abstract-members
I propose we allow it because it's necessary when base class has protected constructor.
The existing way of approaching this problem in F# is ...
Define top level class that only invokes base constructor.
Pros and Cons
The advantages of making this adjustment to F# are ...
Better inter-op with existing NET libraries.
The disadvantages of making this adjustment to F# are ...
Extra work.
Extra information
Estimated cost (XS, S, M, L, XL, XXL):
No idea.
Affidavit (please submit!)
Please tick this by placing a cross in the box:
- [x ] This is not a question (e.g. like one you might ask on stackoverflow) and I have searched stackoverflow for discussions of this issue
- [ x] I have searched both open and closed suggestions on this site and believe this is not a duplicate
- [ x] This is not something which has obviously "already been decided" in previous versions of F#. If you're questioning a fundamental design decision that has obviously already been taken (e.g. "Make F# untyped") then please don't submit it.
Please tick all that apply:
Described here
https://stackoverflow.com/questions/8154730/object-expression-for-abstract-class-without-abstract-members
I propose we allow it because it's necessary when base class has protected constructor.
The existing way of approaching this problem in F# is ...
Define top level class that only invokes base constructor.
Pros and Cons
The advantages of making this adjustment to F# are ...
Better inter-op with existing NET libraries.
The disadvantages of making this adjustment to F# are ...
Extra work.
Extra information
Estimated cost (XS, S, M, L, XL, XXL):
No idea.
Affidavit (please submit!)
Please tick this by placing a cross in the box:
Please tick all that apply: