Open questions
Each is an issue, labelled language and decision, which holds its discussion; those settled keep their answer here.
- Leaving an arena. #25
- Locales. #26
- Byte order of a bit field. #27
-
inon flags. #28 - Syntax extensions. #29: none beyond prefixed literals (5.4). Keywords or notations imported per module, à la Lean 4, would make a file unreadable without resolving its imports, and weigh on the compiler, the formatter and the language server alike; literals over several lines are #66.
- Cost of meta code. #30
- Assembly bodies. #31
- Annotations applied by aspect #32
- Properties. Named projections (6.3):
property count(self): Intand itsmut selfform, whose read can record a dependency and whose write notifies after itsyield. Still open: whether the IDE marks an assignment that runs code (principle 5); whatwith,..source, record patterns and meta’st.fieldsshould see of a property; a property computed without a location, written by distributing the value. - References with identity. Settled by memory-model.md, section 7: a
shared mut Tvalue andweakfields (6.4); a graph one owner holds is an arena object. - Copy-on-write sharing. #33
- Views and arenas. #34
- Interoperability. #35