Pieter12345

I believe that the problem here is that a variable declaration (without assigned value) has a non-void return value. Making this return void would fix this issue and make more...

Given that the code works, I like the following changes: - Added some "extends MCPlayerEvent" to interfaces where applicable. - Removed static warmup() call, so methods are only cached when...

Just to clarify, the compile errors are valid, only the source (`Target`) should be known here instead. Regarding the note: It is indeed true that you can currently use classtypes...

This bug is caused by using singular cached `CClassType`s with an unknown target. These are created [here](https://github.com/EngineHub/CommandHelper/blob/master/src/main/java/com/laytonsmith/core/MethodScriptCompiler.java#L1688). One possible fix is to not use cached `CClassType`s when a target for...

This comes with the question what the default behavior should be, and what should be allowed as a default argument. The main thing to consider language-design-wise is whether dynamic default...

If we want to make this work like the first code example from @LadyCailin, which I think is reasonable, then what we should do is store the optimized AST of...

That brings up an extra difficulty to handle. If a compile-time evaluated function results in a non-primitive, should that result in the same reference being passed into all proc calls...

Keeping in mind that default arguments can be complex and contain closures, procs, binds, ... with their own scoping rules, it is not straight-forward to select which variables should be...

If MS will eventually become aware of statements and expressions (in compile time would be sufficient), then only allowing an expression there would make sense. However, `assign()` currently is an...

What we can do is scan the AST and keep a list of variable names that are used within there. That can function as a filter that does help, but...