Novus Nota
Novus Nota
Here on GitHub, we can do such a simple and free workflow — whenever someone pushes their changes into the `master` branch: 1. There would start a GitHub Actions workflow...
Adding a Tact programming language for `.tact` file extension and an extension to JSON under `.tact`. More about the former: https://tact-lang.org/ ## Description Tact is a new programming language for...
Adding an Ohm language for `.ohm` extension. Expected to only occur once per repo. ## Description Ohm is a parsing toolkit consisting of a library and a domain-specific language. One...
For example, see how JetBrains made their template for new plugins: https://github.com/JetBrains/intellij-platform-plugin-template#getting-started Basically, upon the instantiation from the template a special CI runs, which updates the README, configuration and self-destructs...
As discussed here: https://github.com/tact-lang/tact-template/pull/10#issuecomment-2093136236
Would greatly help with #183. The basic idea is to move from the current Ohm-generated parser to a standalone one, which would be suitable for tools like Language Server or...
See: https://github.com/tact-lang/tact-docs/issues/191#issuecomment-2080458938
It would greatly benefit for tools to be able to get results of the compilation without waiting for the whole `build()` to complete with all the wrappers and following. Just...
Instead of: ```tact message SomeMsg { iField: Int; sField: String; } receive(msg: SomeMsg) { let first: Int = msg.iField; let second: Int = msg.sField; } ``` we could have the...
Basic idea follows similar formats, see [JSDoc](https://github.com/jsdoc/jsdoc), [JavaDoc](https://docs.oracle.com/en/java/javase/21/javadoc/javadoc.html) or [dart doc](https://dart.dev/tools/dart-doc) (the tool I think it should be based off of) — to be able to write documentation comments for...