Yehuda Katz

#[derive(new)] on non-pub struct should give `fn new` the right visibility (required for 2018 idioms)

3

Today, `#[derive(new)]` always creates a `pub fn`, regardless of the visibility of the struct it's applied to. In Rust 2018, that becomes a lint error, which makes it (at present)...

- [ ] Custom package-wide prelude

This is an in-progress, low-level language that natively targets WebAssembly. ``` C:asm :: this:wasm ``` # Low Level Vision Statement It avoids facilities like universal garbage collection or universal virtual...

# A list of important technical properties, as of the beginning of this project: - works ergonomically without a garbage collector - has an ownership model, like Rust and Pony...

# Philosophy - Beginner-friendly is not in conflict with power for experienced developers - Layer conventional systems on top of [sharp tools][sharp-knives] - Optimize for programmer happiness - Enable abstractions...

- [ ] Correctly infer number literals - [ ] Correctly infer all variables - [ ] Type checking - [ ] Add closures - [ ] Add type aliases...

Conversion to proc_macro2::Literal

5

I've started writing a conversion from `(litrs::Literal, Span)` to `proc_macro2::Literal`, and was wondering if there was a trick for doing it (given that `Literal` only has a ton of constructors...

Suggest Alternate Resolution Strategy

1

I personally use a different resolution strategy for both migrations and bundler. # Bundler 1. As of sometime in 1.0, it should be fine to always run `bundle install` without...

Update to more recent Rust

1

## replace proc_macro_hack with proc_macro This allows nested macro executions (and therefore allows macros in other crates to abstract the gen macros). ## add rust-toolchain with nightly toolchain Otherwise, `cargo...

Allow #![] attributes to work in 0.16

11

In 0.16, the default mode for lalrpop will import the generated module through a macro that `include!`s the contents. PR #338 made it possible to use `include!` with vanilla modules...