>>>>> "GvR" == Guido van Rossum <guido@digicool.com> writes:
GvR> Barry, you were supposed to throw a brick at me with this
GvR> content at the meeting, on Eric's behalf. Why didn't you? I
GvR> was waiting for someone to explain why this was a big idea,
GvR> but everybody kept their face shut! :-(
I actually thought I had, but maybe it was a brick made of bouncy spam
instead of concrete. :/
GvR> I'm not sure this is viable. I believe Jeremy's compiler
GvR> package actually doesn't have its own parser -- it uses the
GvR> parser module (which invokes Python's standard parse) and
GvR> then transmogrifies the parse tree into something more
GvR> usable, but it doesn't change the syntax! Quixote can get
GvR> away with this because their only change is giving a
GvR> different meaning to stand-alone string literals. But for
GvR> type annotations this doesn't give enough freedom, I expect.
I thought PTL definitely included a "template" declaration keyword, a
la, def, so they must have some solution here. MEMs guys?
-Barry
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