Enso2023
From APIDesign
(Difference between revisions)
| Line 3: | Line 3: | ||
* suggest language changes | * suggest language changes | ||
* change the infrastructure to work better | * change the infrastructure to work better | ||
| + | |||
| + | == Tooling == | ||
| + | |||
| + | * [https://github.com/enso-org/enso/pull/4014 Basic VSCode support for Enso language and development] | ||
| + | * [https://github.com/enso-org/enso/pull/4015 Basic IGV Scala Support] | ||
| + | * Integration with VisualVM - [https://github.com/enso-org/enso/pull/4110 write logs in XML] & co. | ||
| + | == Improving language == | ||
| + | |||
| + | * Making it really immutable - like [https://github.com/enso-org/enso/pull/4023 Removing Unsafe.set_atom_field] | ||
| + | |||
| + | |||
List of [https://github.com/enso-org/enso/issues?q=state%3Aclosed%20author%3Ajaroslavtulach%20closed%3A2023%20sort%3Acreated-asc 252 issues and requests] resolved in 2023. | List of [https://github.com/enso-org/enso/issues?q=state%3Aclosed%20author%3Ajaroslavtulach%20closed%3A2023%20sort%3Acreated-asc 252 issues and requests] resolved in 2023. | ||
Revision as of 06:50, 30 April 2026
Another year at Enso. I think I started to feel more confident about the code base than in Enso2022 and was able to start designing:
- propose architectural changes
- suggest language changes
- change the infrastructure to work better
Tooling
- Basic VSCode support for Enso language and development
- Basic IGV Scala Support
- Integration with VisualVM - write logs in XML & co.
Improving language
- Making it really immutable - like Removing Unsafe.set_atom_field
List of 252 issues and requests resolved in 2023.
Follow
