Enso2023

From APIDesign

(Difference between revisions)
Jump to: navigation, search
Line 3: Line 3:
* suggest language changes
* suggest language changes
* change the infrastructure to work better
* change the infrastructure to work better
 +
 +
== Performance ==
 +
 +
* [https://github.com/enso-org/enso/issues/6100 Speed Standard.Base initialization in simple Hello World example up!]
== Tooling ==
== Tooling ==
Line 9: Line 13:
* [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.
 +
== Improving language ==
== Improving language ==
* Making it really immutable - like [https://github.com/enso-org/enso/pull/4023 Removing Unsafe.set_atom_field]
* Making it really immutable - like [https://github.com/enso-org/enso/pull/4023 Removing Unsafe.set_atom_field]
 +
* [https://github.com/enso-org/enso/pull/6151 Suspended atom fields are evaluated only once]
 +
 +
== Improving Libraries ==
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:54, 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

Tooling

Improving language

Improving Libraries

List of 252 issues and requests resolved in 2023.

Personal tools
buy