This is a tracking issue for unstable syntax that is currently not supported. I think it is OK to add support for some of these before it is stabilized, as long as the changes aren't too invasive (and can be easily backed out or changed if the feature changes before it is stabilized). This issue is mainly intended as a heads-up for things on the horizon.
[ ] 7. "default" keyword for specialization. RFC 1210issue 31844. Still unsettled.
default fn f() {}
default impl Trait for X {}
[x] 8. const generics (such as strings in generic args, etc.). (#451)
This list is far from complete, but covers a few things I'm aware of and are under active development. If anyone knows of something to add, please add a comment.
This is a tracking issue for unstable syntax that is currently not supported. I think it is OK to add support for some of these before it is stabilized, as long as the changes aren't too invasive (and can be easily backed out or changed if the feature changes before it is stabilized). This issue is mainly intended as a heads-up for things on the horizon.
storage.modifier
scope in thevisibility
context.vis
macro designator. Issue 41022, now stabilized.This list is far from complete, but covers a few things I'm aware of and are under active development. If anyone knows of something to add, please add a comment.