Back to Questions
869
views1
comment
Too much freedom when choosing between "override" "default" and "member"
f#

According to the spec:

[link:research.microsoft.com]

"Members that implement dispatch slots on the base

type must be declared

using override or default, and those that implement dispatch slots on interface

types must be

declared under an interface implementation and may use member,

override or default.. The

keywords override and default are synonyms."

My question is:

1) Why are you allowed to choose between "member" and "override" when implementing interfaces, why not just settle on "member" ?

2) Why are "override" and "default" synonyms?

.

The recommendation is to use "member" in interface implementations. We will adjust the spec to make that clear. We do allow the use of "override" to allow transitions between

concrete member implementations <--> interface programming <--> abstract member implementations

However using "member" is normal in F#.

Having both "default" and "override" allows the user to record the intended role of the member implementation. Recommended coding style is to use "default" when the abstract slot is in the same class, and otherwise use "override". We will also make that clearer in the spec.

We have a suggestion open to check these in a future version via an opt-in warning.

Thanks for the feedback,

Don

By on 3/29/2010 9:04 AM ()

    Topic tags

    IntelliFactory Offices Copyright (c) 2011-2012 IntelliFactory. All rights reserved.
    Home | Products | Consulting | Trainings | Blogs | Jobs | Contact Us | Terms of Use | Privacy Policy | Cookie Policy     		Built with WebSharper