We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I propose using \ as a simple syntactic sugar for generics with a single type parameter.
\
The two following types are equivalent:
Bar<T> Bar\T
This might make nested types simpler avoiding the long >>>> tail, and look like a directory tree. A made up example with two equivalent types below
>>>>
Ref<Box<RawPtr<T>>> Ref\Box\RawPtr\T
The generics with several type parameters can be used as usual:
Box<Result<E<String>, RawPtr<Box<T>>>> Box\Result<E\String, RawPtr\Box\T>
Any token can be used for the nesting, not necessarily \, the / could be used as well, as long as it does not introduce confusion.
/
The text was updated successfully, but these errors were encountered:
🤔 I don't really see why this would be necessary tbh, you rarely need to name things like this and your scheme only saves one character...
Sorry, something went wrong.
No branches or pull requests
I propose using
\
as a simple syntactic sugar for generics with a single type parameter.The two following types are equivalent:
This might make nested types simpler avoiding the long
>>>>
tail, and look like a directory tree. A made up example with two equivalent types belowThe generics with several type parameters can be used as usual:
Any token can be used for the nesting, not necessarily
\
, the/
could be used as well, as long as it does not introduce confusion.The text was updated successfully, but these errors were encountered: