lily

KO | EN

gitlite — search

#javascript #hacktoberfest #react #ai #go #rust #deep-learning #java #awesome #kubernetes #awesome-list #ios #openai #mcp

(★ 1,093)

Interpreted language focused on expressiveness and type safety.

File Explorer

Download Latest Version (.zip)

- pkg_core.lily
- pkg_coroutine.lily
- pkg_fs.lily
- pkg_introspect.lily
- pkg_math.lily
- pkg_prelude.lily
- pkg_random.lily
- pkg_subprocess.lily
- pkg_sys.lily
- pkg_time.lily
- pkg_utf8.lily
- CMakeLists.txt
- lily.c
- repl.c
- common.lily
- parser_data.lily
- prelude.lily
- token.lily
- CMakeLists.txt
- csiphash.c
- lily.h
- lily_alloc.c
- lily_alloc.h
- lily_api.c
- lily_buffer_u16.c
- lily_buffer_u16.h
- lily_build_error.c
- lily_closure.c
- lily_closure.h
- lily_code_iter.c
- lily_code_iter.h
- lily_core_types.h
- lily_emitter.c
- lily_emitter.h
- lily_expr.c
- lily_expr.h
- lily_generic_pool.c
- lily_generic_pool.h
- lily_import.c
- lily_import.h
- lily_lexer.c
- lily_lexer.h
- lily_lexer_data.h
- lily_library.c
- lily_library.h
- lily_msgbuf.c
- lily_opcode.h
- lily_parser.c
- lily_parser.h
- lily_parser_data.h
- lily_pkg_core.c
- lily_pkg_coroutine.c
- lily_pkg_coroutine_bindings.h
- lily_pkg_fs.c
- lily_pkg_fs_bindings.h
- lily_pkg_introspect.c
- lily_pkg_introspect_bindings.h
- lily_pkg_math.c
- lily_pkg_math_bindings.h
- lily_pkg_prelude.c
- lily_pkg_prelude_bindings.h
- lily_pkg_random.c
- lily_pkg_random_bindings.h
- lily_pkg_subprocess.c
- lily_pkg_subprocess_bindings.h
- lily_pkg_sys.c
- lily_pkg_sys_bindings.h
- lily_pkg_time.c
- lily_pkg_time_bindings.h
- lily_pkg_utf8.c
- lily_pkg_utf8_bindings.h
- lily_platform.h
- lily_raiser.c
- lily_raiser.h
- lily_string_pile.c
- lily_string_pile.h
- lily_symtab.c
- lily_symtab.h
- lily_token.h
- lily_type_maker.c
- lily_type_maker.h
- lily_type_system.c
- lily_type_system.h
- lily_utf8.c
- lily_utf8.h
- lily_value.h
- lily_virt.c
- lily_virt.h
- lily_vm.c
- lily_vm.h
- st.c
- - bench.lily
  - binary_trees.lily
  - binary_trees.lua
  - binary_trees.py
  - binary_trees.rb
  - fib.lily
  - fib.lua
  - fib.py
  - fib.rb
  - for.lily
  - for.lua
  - for.py
  - for.rb
  - map_numeric.lily
  - map_numeric.lua
  - map_numeric.py
  - map_numeric.rb
  - map_string.lily
  - map_string.lua
  - map_string.py
  - map_string.rb
  - README.md
  - test_benchmark.lily
- - test_bad_call.lily
  - test_bad_keyargs.lily
  - test_bad_optargs.lily
  - test_call_pipe.lily
  - test_keyargs.lily
  - test_optargs.lily
  - test_varargs.lily
- - test_bad_class.lily
  - test_class.lily
- - test_verify_closures.lily
- - test_verify_constant.lily
- - nul_in_file.lily
  - test_dynaload.lily
  - test_verify_coverage.lily
- - test_bad_enum.lily
  - test_enum.lily
- - test_bad_exception.lily
  - test_exception.lily
- - test_verify_format.lily
- - test_bad_forward.lily
  - test_forward.lily
- - test_verify_gc.lily
- - enum_export_main.lily
  - enum_export_user.lily
  - enum_exporter.lily
  - rooted_base.lily
  - test_bad_import.lily
  - test_import.lily
- - content.lily
  - inspection.lily
  - test_verify_inspection.lily
- - test_bad_lambda.lily
  - test_lambda.lily
- - test_bad_manifest.lily
  - test_manifest.lily
- - test_bad_matchwith.lily
  - test_matchwith.lily
- - test_boolean.lily
  - test_byte.lily
  - test_bytestring.lily
  - test_file.lily
  - test_hash.lily
  - test_integer.lily
  - test_list.lily
  - test_option.lily
  - test_result.lily
  - test_string.lily
- - test_pkg_coroutine.lily
  - test_pkg_fs.lily
  - test_pkg_introspect.lily
  - test_pkg_math.lily
  - test_pkg_random.lily
  - test_pkg_subprocess.lily
  - test_pkg_sys.lily
  - test_pkg_time.lily
  - test_pkg_utf8.lily
- - test_verify_rewind.lily
- - test_verify_sandbox.lily
- - test_bad_syntax.lily
  - test_bad_token.lily
  - test_basics.lily
- - testing.lily
- - test_generics.lily
  - test_inference.lily
  - test_narrowing.lily
  - test_quantification.lily
  - test_scoop.lily
  - test_variance.lily
- - test_bad_virt.lily
  - test_virt.lily
- CMakeLists.txt
- file_for_io.txt
- test_driver.c
- coroutine_tasks.lily
- fib.lily
- fizzbuzz.lily
- one_hundred_doors.lily
- rpn_calculator.lily
- show_classes.lily
- show_how_to_combine_functions.lily
- show_off_enums.lily
- sum_numbers_from_argv.lily
.appveyor.yml
.gitignore
.gitlab-ci.yml
CMakeLists.txt
Findlily.cmake
LICENSE.txt
README.md
RELEASES.md

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

[![Discord](https://img.shields.io/discord/1416899236196253850)](https://discord.com/invite/yxspNFzfDv)
[![Pipeline Status](https://gitlab.com/FascinatedBox/lily/badges/main/pipeline.svg)](https://gitlab.com/FascinatedBox/lily/-/commits/main)
[![Windows Build](https://ci.appveyor.com/api/projects/status/gitlab/FascinatedBox/lily?svg=true)](https://ci.appveyor.com/project/FascinatedBox/lily)
[![Coverage Report](https://gitlab.com/FascinatedBox/lily/badges/main/coverage.svg)](https://FascinatedBox.gitlab.io/lily/src/index.html)

## Lily

Lily is a programming language focused on expressiveness and type safety.

## Sample

```
scoped enum Color { Black, Blue, Cyan, Green, Magenta, Red, White, Yellow }

class Terminal(public var @foreground: Color, width_str: String)
{
    public var @width = width_str.parse_i().unwrap_or(80)

public define set_fg(new_color: Color) {
        @foreground = new_color
    }
}

var terms = [Terminal(Color.White, "A"), Terminal(.Red, "40")]

terms.each(|e| e.width += 20 )
     |> print
```

## Features

#### Embeddable

Lily may be a statically-typed language, but the reference implementation is an
interpreter. The interpreter as well as its API have been carefully designed
with sandboxing in mind. As a result, it's possible to have multiple
interpreters exist alongside each other.

#### Shorter edit cycle

Another benefit from having the reference implementation as an interpreter is a
shorter turn around time. The interpreter's parser is comparable in speed to
that of languages using an interpreter as their reference.

## Building

You need a C compiler (C11+) and CMake (3.10+). There are no external dependencies.

To build Lily, execute the following in a terminal:

```
cmake .
cmake --build .
```

Note: Windows users may need to add `-G"Unix Makefiles"` to the end of the cmake
invocation.

The above will build the `lily` executable, as well as a liblily that you can
use with your program. It also builds `pre-commit-tests`.

## Running tests

The centerpiece of Lily's testing is `test_main.lily` in the `test` directory.
That file imports and invokes a large number of tests that cover a lot of Lily.

The `make` command also builds `covlib` and `pre-commit-tests`. No additional
commands are necessary. `covlib` is a library that tests some parts of Lily that
native code can't test. `pre-commit-tests` is a special runner that executes
`test_main.lily`.

To run Lily's tests, execute `pre-commit-tests` from the directory it's in after
building Lily.

## Resources

* [Documentation](http://lily-lang.org)

* [Builtin module reference](http://lily-lang.org/core/module.core.html)

* [Try it in your browser](http://lily-lang.org/intro-sandbox.html)

## Packaging

The [lily-garden](https://gitlab.com/FascinatedBox/lily-garden) repository
contains a package manager (Garden) that simplifies the install of Lily
packages.

## License

[MIT](https://gitlab.com/FascinatedBox/lily/blob/main/license.txt)

lily

File Explorer

Today's picks

Was this content helpful?

Recent Feedback

lily

File Explorer

Today's picks

Was this content helpful?

Recent Feedback

Download README