Here I have another suggestion, this time about our Gravity's CLI. I come up with this list of improvements which I think should benefit the project:

• If no arguments passed it should display help section instead of opening REPL
• To open REPL add a new flag for example gravity --repl
• gravity new [project] - a new simple command to create new project. (A wizard which helps with co

These are the feedback from @yawniek on slack

• the vm.New vm.New and v.ExecInstructions methods would profit from some minimal documentation, especially what all the "paths" actually mean. some of them seemed semi obvious..
• same for RegisterExternalClass ExternalClass and vm.Method albeit those are relatively clear
• how can i load a class into toplevel so i dont need a requir

We need a contributing.md doc that shares community conventions.

Stamp conventions

• Naming stamps: your-module-name-stamp
• Keywords for package.json: stamp, stampit

Automatic code quality conventions 😎

• Use the prod-module-boilerplate (soon to be replaced with `npm install -g cloverfield cf-package

https://github.com/eclipse/eclipse-collections/blob/master/docs/guide.md#-primitive-collections

• C
• C++
• C# - @ajaynair710
• CoffeeScript
• Dart - @Valdermaut
• Go
• Java
• JS - @ashishnagpal2498
• Kotlin - @sandhyabhan
• Php
• Python
• Readme - @SimranMakhija7
• Ruby
• Rust
• TypeScript - @aaliyah03

Reason

Many postprocessors which were developed before newer APIs came about do their communication in getValue(). With the finalize() method added, we suggest that communication is done there instead.

Design

Move communication calls from getValue() to finalize() for postprocessors where possible.

Impact

Consistency across postprocessor objects.

On the main page, the documentation talk about using ref_ptr for memory management, but none of the code does that. It's not clear what is the current memory model expectation from globjects now it's using unique_ptr, so I guess a update of the documentation is required.

It should answer these questions:

1. When the globject interface use a plain pointer, who is managing the pointer life

I want to write feedback as a user who used the framework, maybe you need it.
It is a framework that can have great skills in the future as I think, perhaps will compete with Vaadin. It's a good thing you support him. It would be very good to have documentation with live examples (no only code), such as within the yested framework (see here) which is

@lberti could you commit the falling sphere case (geo+cfg+json) ?
please add a README.adoc to explain the expected results

@vincentchabannes needs it to test new developments

The repository https://github.com/daokoder/learnxinyminutes-docs needs some love.

1. The repository does not currently contain Dao. The page https://learnxinyminutes.com/ already saved a lot of time to many people I know and now I need few good programmers to learn Dao, but they have to dig through the incomplete "long" documentation, which does not make t

• Elementary cellular automaton
• Zebra puzzle
• Write float arrays to a text file
• Word search

I'm pretty sure that SimpleAssign is only created when the left-hand side is a StaticAssignable (e.g., Var, Const, or Underscore). If the target is a pattern, then it becomes a MatchAssign, and if it is some method chain (e.g. x.y = 2), then it is converted into a Call to the y= method with x as the receiver.

With that, I think that the target property of SimpleAssign no