Enso2023

From APIDesign

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 1 Performance and Runtime 2 Tooling 3 Improving Language 4 Improving Libraries

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 <|
  • ... on (GraalVM EE)
  • ... on GraalVM CE!!!

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

• Consolidate Vector and Array methods

List of 252 issues and requests resolved in 2023.