Skip to content

Stdlib: introduce `Test.Next`

E. Rivas requested to merge er433/lib/test-next into dev

Motivation and Context

Test library grew in a disorganized way, not deprecating/renaming/moving anything, to avoid breakage.

Description

This MR introduces Test.Next, a submodule to Test that is a re-organization, and that could be used to replace Test.

For now, we avoid using include, as there are some performance issues related to it.

Component

  • compiler
  • website
  • webide
  • vscode-plugin
  • debugger

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Performance improvement (non-breaking change that improves performance)
  • None (change with no changelog)

Changelog

This MR introduces Test.Next, a submodule to Test that is a re-organization, and that could be used to replace Test.

For now, we avoid using include, as there are some performance issues related to it.

Checklist:

  • If a new syntax has been introduced, put a message on slack ligo-lsp
  • Changes follow the existing coding style (use dune @fmt to check).
  • Tests for the changes have been added (for bug fixes / feature).
  • Documentation has been updated.
  • Changelog description has been added (if appropriate).
  • Start titles under ## Changelog section with #### (if appropriate).
  • There is no image or uploaded file in changelog
  • Examples in changed behaviour have been added to the changelog (for breaking change / feature).
Edited by Laurent Canis

Merge request reports