exyi / coberec Goto Github PK

• Classic for - for(Init; Cond; Body1) { Body2 }
• int/long incremental cycle for - for(var i = 0; i < len; i++) { Body }
• int/long decrement long for - for(var i = len; i >= 0; i--) { Body }

Probably best done by something like FunctionExpression, but resulting in a System.Linq.Expressions.Expression<X>

Automatic symbol renaming may change existing symbol names when the code is re-regenerated. We should introduce a simple key-value lock file, that will force the code generator name the symbols specifically to prevent breaking changes in a generated API.

This is currently possible though declaring static methods, but we should have helpers for it.

We need to add attributes field to every MemberDefinition + add a method to MetadataContext to add assembly attributes.

No idea how, and probably not a big deal. Can be emulated by emitting the dynamic code with [Dynamic] attribute

Maybe, we could have a lifting validator validateArray(validator: "notEmpty")

pointer to reference, reference to pointer, fixed, stackalloc

Currently, we just use what the project is set to use.

The best way is probably to introduce a Checked/Unchecked blocks that will override the default inside of them. The alternative is to put a flag to the BinaryOperatorExpression

Add a flag to the MethodParameter type.

Low priority, and I don't have an idea how it should work.

Probably best done though ConstantExpression supporting TypeReference, SpecializedType, TypeSignature and the System.Reflection.Type itself.

Probably best to be implemented through lowerable expression with a rewriting pass - for the omision of IEnumerable<T> boxing

The best way is probably to add a flag to ReferenceConversionExpression specifying if it should throw exception or return null - i.e. behave as cast or behave as the as keyword.

Just a flag on FieldSignature

It is currently not possible to declare events.

Currently, when an empty constructor is declared it does not even call the base(), which is done implicitly by C#. We should add a validation step that will ensure that there is exactly one base() invocation. Maybe, we can add the call implicitly, if there is none.