Guido van Rossum wrote:
> > def C as class:
> > suite
>
> Um, the whole point of this syntax is that property, synchronized
> etc. do *not* have to be keywords -- they are just callables.
How many different types of parsing are needed? Could
some small number of keywords that determine how the
thunk is parsed be intermixed in the same context as
the thunk-aware objects?
def C(B) as class:
def spam() as staticmethod function: ...
def spamspam(klass) as classmethod generator: ...
def spamspamspam as class property: ...
-Jerry
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4