Solution to forward references

[TobiasHT5]

So I think we've faced the problem of forward referencing first-hand. I used to hear about it in the typing world but I'd never given it much thought till today. Fortunately there were solutions that were designed for it. we're going to use the typing.TYPE_CHECKING constant and also the __future__.annotations feature. example

from __future__ import annotations

from typing import TYPE_CHECKING,

if TYPE_CHECKING:
     from .message import Message


def foo() -> Message:
     ...

if we put our controversial imports under TYPE_CHECKING, they will be blocked from the runtime environment but available to the type checker, which will work for us. so this is the way to go around the forward referencing.
@kallyas @edger-asiimwe @ushergodwin

[TobiasHT5]

Is there a scenario where this is needed? in any case, if you import annotations from __future__, then it shall be fixed.

[TobiasHT5]

All in all, let's try to fix up what we can, at least to first get rid of the nasty import cycles so that we move on to the next task. We can continue typing any other time.

[kallyas]

Is there a scenario where this is needed? in any case, if you import annotations from future, then it shall be fixed.

Yes, The Message Object

[TobiasHT5]

@kallyas I didn't get any errors doing something like this

class Test:
    def __init__ (self):
        self.att:Test = None

I'm sorry, I think I deleted the initial comment you had written by mistake, cause I can't seem to find it

[kallyas]

Fo

@kallyas I didn't get any errors doing something like this

class Test:
def init (self):
self.att:Test = None
I'm sorry, I think I deleted the initial comment you had written by mistake, cause I can't seem to find it

For that, I fixed it later on