diff --git a/Feature-Matrix.md b/Feature-Matrix.md new file mode 100644 index 0000000..1635435 --- /dev/null +++ b/Feature-Matrix.md @@ -0,0 +1,269 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Language featureScheduled forNotes
Automatic dereference in more contexts0.9.6important to be able to write more generic containers easily
support overloading of the assignment operator0.9.6like fields and destructors an assignment operator needs to be lifted
destructors need to interact with finalizers0.9.6destructors and finalizers are implemented, but do not interact. new which takes a finalizer needs to be deprecated. People should use a destructor instead
the new concurrency model0.9.6this requires frontend and backend changes, but no changes to the runtime/GC
weaken the requirements for forward declarationsafter 1.0two different design ideas exist: one conservative and so will work, the other highly experimental
comment handling is weird0.9.6comments should be optional and not part of the grammar, unless it is a documentation comment
push pragma needs to be reworkedafter 1.0it should be distinguished between 'push' for 'type', 'proc' etc.
pragmas are not supported for 'bindSym'0.9.6this makes clean macros impossible to write when it comes to pragmas
type checking for tuples0.9.8needs to be refined. Recursive tuples should be forbidden.
extended macros API0.9.8missing: an API for working with types; the builtin getImpl
write tracking0.9.8algorithm exists. Can be extended to compute lent pointers.
prevent object branch transitions from low(selector)after 1.0object branch transitions from low(selector) are allowed, because they are simply too useful, but can break memory safety. Now that the language has a proper notion of construction, we can make them safe.
~ operator for effectsafter 1.0it is not entirely clear what ~F should mean.
some effects like GCMem don't need to be white-listedafter 1.0unclear whether this only affects built-in properties like GCMem, Recursive.
returning 'var T' is unsafe and needs static analysis to make safeafter 1.0the compiler already checks for trivial examples
alias analysis needs to specified and controllable with pragmasafter 1.0alias analysis affects memory safety rules
term rewriting macros need more loveafter 1.0we need much more tests and use them in production
Compiler featureScheduled forNotes
high level optimizerafter 1.0use the effect system for optimizations; interacts with TR macros; + performs:
    +
  • GCSE
  • + +
  • loop invariant hoisting
  • + +
  • escape analysis for string/seq
  • + +
  • inlining of small lambdas
  • + +
+ +
pure RC'ing GCafter 1.0important for better interoperability with Objective-C
GPU backendafter 1.0
symbol filesafter 1.0
deterministic code generation0.9.8