Enso2023

From APIDesign

(Difference between revisions)
Jump to: navigation, search
Line 4: Line 4:
* change the infrastructure to work better
* change the infrastructure to work better
-
== Performance ==
+
== Performance and Runtime ==
* [https://github.com/enso-org/enso/issues/6100 Speed Standard.Base initialization in simple Hello World example up!]
* [https://github.com/enso-org/enso/issues/6100 Speed Standard.Base initialization in simple Hello World example up!]
* [https://github.com/enso-org/enso/issues/6191 Any.== slowed down by gigantic EqualsNode specializations]
* [https://github.com/enso-org/enso/issues/6191 Any.== slowed down by gigantic EqualsNode specializations]
 +
* [https://github.com/enso-org/enso/pull/6335 Removing need for asynchronous thread to execute ResourceManager finalizers]
 +
* Improve inlining of '''<|'''
 +
** [https://github.com/enso-org/enso/pull/6384 ... on (GraalVM EE)]
 +
** [https://github.com/enso-org/enso/issues/6416 ... on GraalVM CE]
== Tooling ==
== Tooling ==
Line 15: Line 19:
* 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]

Revision as of 07:00, 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

Tooling

Improving Language

Improving Libraries


List of 252 issues and requests resolved in 2023.

Personal tools
buy