rune

rune copied to clipboard

It'd be very nice to have an auto-formatter for Rune which can take a source-snippet and format it properly.

tgolsson

feature: support monomorphization and jitting

2

This is a topic I've been thinking about for a while based on the following observations: * Value conversions take an observable amount of time in flamegraphs * Function lookup...

tgolsson

For example, the LSP could expose commands to run, check, or test the current code by sharing some code with rune-cli. Potentially has some overlap with DAP, for debugging capabilities.

tgolsson

In order to provide good diagnostics it'd be helpful if the DebugInst not only pointed to the span of the *instruction* but also any related parts that are useful for...

tgolsson

Currently, a lot of tests are Rust tests that execute a single script to validate the language. In order to dogfood the language capabilities we could migrate some of these...

tgolsson

Use dynamically dispatched generics to reduce namespace contamination

1

Come up with a generics scheme that works at runtime and allows for: * Dynamically dispatching a function call to the correct implementation depending on the type of the arguments....

udoprog

For example: ```rust #[derive(runestick::Any, Default)] struct MyObject

sapir

Macros in statement positions might produce expressions *or* statements. This causes issues if the macro produces an item, because items need to be indexed *before* macros using them in case...

udoprog

This will be required for native items (functions, types, macros, ...) to be known by the language server so that they can compile without having to load the native modules...

udoprog

Support const evaluation

1

Support constant expressions, like these:x ```rust const VALUE = #{hello: "World"}; ``` They can reference other constant expressions, but will fail to compile if there are cycles: ```rust const VALUE...

udoprog