Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[new release] lice (0.0.1-dev) #25812

Closed
wants to merge 1 commit into from

Conversation

gabyfle
Copy link

@gabyfle gabyfle commented May 7, 2024

The Lice Programming language libraries and interpreter

CHANGES:

This is the first version with a working prototype of the Lice interpreter using bytecode and a virtual machine instead of a tree-walk algorithm. Improvements have been made on memory usage and execution times.

Modified

  • Switched the whole interpreter to a bytecode interpreter. This should
    improve performance and reduce memory usage.

  • Changed the way the lice library and the interpreter is compiled, making Lice a true OCaml library.

  • Reformated the way types works inside the language and made an overall code cleanup.

  • Functions are first class citizens.

Fixed

  • Fixed the lexing of float numbers.

Note: This is a pre-release and it's not intended to be used yet.

CHANGES:

This is the first version with a working prototype of the Lice interpreter using bytecode and a virtual machine instead of a tree-walk algorithm. Improvements have been made on memory usage and execution times.

### Modified

- Switched the whole interpreter to a bytecode interpreter. This should
  improve performance and reduce memory usage.

- Changed the way the lice library and the interpreter is compiled, making Lice a true OCaml library.

- Reformated the way types works inside the language and made an overall code cleanup.

- Functions are first class citizens.

### Fixed

- Fixed the lexing of float numbers.

Note: This is a pre-release and it's not intended to be used yet.
@mseri
Copy link
Member

mseri commented May 13, 2024

I think the version may not be correct: you are trying to release version 0.0.1-dev but shouldn't it be 0.0.1? Also note that 0.0.1-dev version value is greater than 0.0.1. If you want to release an alpha, a beta or if you prefer a "dev" version, you should probably use 0.0.1~dev or 0.0.1~alpha1 (the latter is more commonly used to emphasize the pre-release nature, although this is usually the expectation for a package with version 0.0.1)

@mseri
Copy link
Member

mseri commented May 13, 2024

If instead you don't want users to install it, then I think it is too early to release it

@gabyfle
Copy link
Author

gabyfle commented May 13, 2024

@mseri Yes, actually it was also to test out the way publishing packages on opam works, as it was my first time doing it. Also, it looks like the flambda backend can't terminate the compilation when -O2 flag is on.

I'll just close this pull request for the moment and create a new one once this is ready for a real release ! Thanks for your time !

@gabyfle gabyfle closed this May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants