Comment by jiaren wang (JIRA)

I would like give a shot on this. Could I get some hint?

If I understand it correctly, the idea it here

class D: C {
   - override func canBecomeFirstResponder() -> Bool {
   - }
   + override var canBecomeFirstResponder: Bool {
   + }
}

Since the override attempt have the same name and the same is a no-args function that produce the same result as the base class property (Bool).

Swift Mentorship program mentee here, trying to contribute for the first time. Will dive deeper and work on this 😁

Hello @AnthonyLatsis - is this issue still open, can I give it a shot? Thanks!

You’re welcome to! Make sure it still reproduces though. Want we to assign you?

I got busier and did not complete it yet, but I did make progress on this and was planning on opening the PR soon.

https://github.com/danielfalbo/swift/tree/fixit-override-func-that-should-be-override-var

Update: I don’t think I’ll keep working on this anytime soon, I’m unassigning myself

Let's try this!

Hey @LucianoPAlmeida @AnthonyLatsis , I managed to find the error call site:
File --> /lib/Sema/TypeCheckDeclPrimary.cpp

(Case 1: When the method is overridden instead of the property)

FD->diagnose(diag::method_does_not_override, isClassContext)
                .highlight(OA->getLocation());

(Case 2: When the property is overridden instead of the method)

VD->diagnose(diag::property_does_not_override, isClassContext)
                .highlight(OA->getLocation());

So I think fixing the actual issue remains. I will try to do it!

@AnthonyLatsis I have a little off-topic issue, I have come across this earlier too, what I did was to delete my workspace and again create it, but is there any other solution to this?

<unknown>:0: error: compiled module was created by an older version of the compiler; rebuild 'Swift' and try again:

PS: Rebuilding fixed the problem!

is there any other solution to this?

This means the binary module format version associated with the just-built compiler is different than the one that was used to serialize the Standard Library (the Swift module). Most likely, you pulled in the latest changes and rebuilt just the compiler (swift-frontend) rather than everything, including the Standard Library. Re-creating the workspace is almost never the answer, because the workspace or the generated Xcode projects are not responsible for building anything — the Ninja build is.

Yes, also one more thing, I am suddenly encountering problems with syntax colouring and type hints not working properly in Xcode files while I am making changes, I tried clearing ~/Library/Developer/Xcode/DerivedData folder too, which could potentially re-index the files, but this isn't still working...

(Some of the text is white, while some of them green, and some are showing few function type hints, not all)

I have always seen these functional issues come up randomly when navigating the code base in Xcode. They usually get worse the older and more outdated the generated project becomes. Re-generating the projects after every checkout is probably the right answer, but I wouldn’t know for certain: I am too lazy to always keep the generated projects in sync, and tend to fall back to searching or spawning tabs whenever these issues show up.

Also, are there any docs related to these specific types of files, meaning, learning about the Types, Decl, etc, to grab the pointers for exactly what I am looking for, or do I have to manually learn and figure out?

Like in this issue, I will have to find a match for the function parameter and its declaration in the parent class, to correctly identify whether this override can be fixed...same goes for the property...

Like in this issue, I will have to find a match for the function parameter and its declaration in the parent class, to correctly identify whether this override can be fixed...same goes for the property...

There is a little bit of info here

Hey thanks a lot @LucianoPAlmeida! Looks like Swift Forums is a good place for asking such doubts!

There is a compiler category on the forums where you can ask more general questions about development in the compiler.
But if those are related to the issue is fine to keep the discussion here or on PRs =]

Cool!

actually when I was looking for type hint

What do you mean by "type hint"? Code completion hints?

Also, are there any docs related to these specific types of files, meaning, learning about the Types, Decl, etc, to grab the pointers for exactly what I am looking for, or do I have to manually learn and figure out?

I do not know of any detailed write-ups on the AST design or the parts of semantic analysis that do not involve subtle and complex algorithms among our docs. This is where the inline documentation and comments come in handy. But we do have a list of external resources, many of which I found very helpful back in the day, with many more yet to read. Check out the article by Slava Pestov about how things are represented in the compiler.

Thanks! @AnthonyLatsis
I will go through the external resources!

Why was this issue closed and re opened?

I have added the notes in the diagnostic file, I hope the changes are relatively fine:
Commits

Have you tested them? Please open a pull request if you want your changes to be reviewed.

Coming soon!

I have one question, regarding the super class inherit, should we consider the case for only one base class or can it be multiple classes, like, for example, class D could inherit from two classes B and C, where the function | property could be from either of them...Maybe an idea would be to limit the number of inherited types to be 2 or 3 considering optimisation?

I finally managed to do it! I just need to provide a fixit now!

Here is the output:

error: method does not override any method from its superclass
    override func canBecomeFirstResponder() -> Bool {
    ~~~~~~~~      ^
note: did you mean to override the property 'canBecomeFirstResponder'?
    override func canBecomeFirstResponder() -> Bool {
                  ^

I have one question, regarding the super class inherit, should we consider the case for only one base class or can it be multiple classes

Swift does not have multiple inheritance.

Oops! My bad! I misinterpreted it with C++ as it has the 'virtual' keyword to handle the diamond problem.