mina

2023-03-01 15:16| 来源: 网络整理| 查看: 265

mina

mina is a minimum viable functional programming language for the JVM.

Everything is currently under construction and subject to change.

The project is a multi-module Gradle project, making use of shared convention plugins in buildSrc/.

The project structure is as follows:

buildSrc/ - this contains shared Gradle build definitions compiler - this subfolder contains subprojects that implement the compiler phases. compiler/common - this contains shared data structures that are used by all compiler phases. Many of these definitions exactly mirror those from the Language Server Protocol. Mina is designed to integrate with LSP, but we don't want to depend on the Java LSP4J library throughout the compiler. compiler/syntax - this contains the definition of the abstract syntax tree and utilities for working with trees. compiler/parser - this contains the ANTLR grammar of the language and the batch-mode parsing phase for namespace definitions. compiler/renamer - this contains the name resolution phase, which is responsible for resolving imports and attributing syntax trees with fully qualified names. compiler/typechecker - this contains the phase responsible for kind-checking data types and type-checking let bindings. compiler/intermediate - unimplemented; this will contain the intermediate language for the compiler optimisation phases. Missing phase folders: compiler/simplifier - this will contain a phase for lowering the user-facing syntax trees into the intermediate language. compiler/optimiser - this will contain a phase for optimising the intermediate language. compiler/jvm - this contains the JVM bytecode generation phase for the compiler, currently only implemented for unoptimised syntax trees. compiler/main - this contains the compiler driver which is responsible for orchestrating compilation of source files. compiler/cli - this contains the command line interface to the Mina compiler, minac. examples - this contains examples of the Mina language syntax. gradle/libs.versions.toml - this is the version catalog declaring dependencies and their versions. See the Gradle documentation about The version catalog TOML file format for more details. gradle-plugin - this contains a Gradle plugin for declaring and building Mina projects. At present it only provides tasks for compiling Mina code. lang-server - this contains an LSP-compatible language server implemented using lsp4j. This server currently implements parsing, renaming, type inference and code generation for the Mina language and displays diagnostics, as well as providing type and kind hover information. Inter-file dependencies are not currently supported. proto - unimplemented, currently nothing more than a copy of the Protobuf definitions from DavidGregory084/inc. This will contain Protobuf definitions for the language syntax and intermediate language. The AST of each namespace will be embedded in its Mina .class file as a custom class file attribute. The optimised intermediate language for definitions will be embedded in Mina .class files for the purposes of inlining. They will serve a similar purpose to Haskell .hi files. vscode-plugin - the VS Code plugin which interacts with the language server in lang-server. Getting started

Prerequisites:

JDK 17+ Node 16+

To get started:

Build the entire project using ./gradlew build publish --info. This also builds the VS Code plugin using gradle-node-plugin and publishes the language server to your local Ivy repository. Open the VS Code extension file in VS Code and hit F5 to launch the Extension Development Host. Try opening the examples/ folder from this project. You can examine the build server logging in the "Mina Language Server" window of the VS Code Output tab. Try making deliberate syntax errors or declaring overflowing numeric literals. Contributing to this project

I think it would be wise to set expectations around contributing to this project: at present it's very much incomplete, amorphous, incubating, and all of the other things that mean a broken and unfinished work in progress, and I have fairly strong opinions about what I would like to achieve.

It would likely be better to wait until the project has solidified a bit and is closer to completion if you'd like to contribute code.

Having said that, I would welcome GitHub discussions about the proposed language syntax, project structure, the name of the project, planned features, suggestions, and anything else you'd like to talk about.

Notes Planned features Major version shading

It's planned that the Mina compiler will have a concept of packages and package versioning, so that it can automatically shade Java packages by major version.

For example, for a namespace mina/data/NonEmptyList, the Java package compiled into the .class file and the group ID used in the dependency metadata will be something like mina.v0.data.

When declaring Mina Gradle projects, the project major version must be declared. When consuming Mina dependencies, the package major version metadata will be used in linking to the underlying .class file definitions.

This should ameliorate the pains of major version migration by allowing dependencies to continue to make use of older major package versions.

The exact details of how this will be implemented are unclear and subject to change.

【本文地址】

公司简介

联系我们