Enso2023
From APIDesign
(Difference between revisions)
(→Performance and Runtime) |
(→Tooling) |
||
| Line 19: | Line 19: | ||
* [https://github.com/enso-org/enso/pull/4014 Basic VSCode support for Enso language and development] | * [https://github.com/enso-org/enso/pull/4014 Basic VSCode support for Enso language and development] | ||
| + | ** [https://github.com/enso-org/enso/pull/7861 Downloadable VSCode extension] | ||
* [https://github.com/enso-org/enso/pull/4015 Basic IGV Scala Support] | * [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. | * Integration with VisualVM - [https://github.com/enso-org/enso/pull/4110 write logs in XML] & co. | ||
Revision as of 07:21, 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
Contents |
Performance and Runtime
- Speed Standard.Base initialization in simple Hello World example up!
- Any.== slowed down by gigantic EqualsNode specializations
- Removing need for asynchronous thread to execute ResourceManager finalizers
- Improve inlining of <|
- Interop with Python and JavaScript and other Truffle languages
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
- Suspended atom fields are evaluated only once
- Designed and implemented runtime type system:
- Clearly report type errors on API boundary
- Automatically apply from conversion when runtime argument check fails - making Enso a conversion oriented language
Improving Libraries
List of 252 issues and requests resolved in 2023.