Kind annotations for type parameters

Open
  • Is something wrong?
#103 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
compilers

Research direction

Start by reading the parser, HIR definition, and type-checking crates: boltlang-parser, boltlang-hir-def, and boltlang-hir-ty. Trace how type parameter kinds are inferred and how [F: ...] bounds are parsed. The syntax is explicitly undecided, so done means settling and implementing a kind annotation syntax that handles parameters whose kinds cannot be inferred, including unused parameters.

Written by the indexing model from the issue text.

Description

discussion enhancement scope:syntax scope:types

The kinds of type parameters are inferred from their uses, and default to Type. Parameters whose kind can't be inferred, like unused ones, need a way to write it. [F: ...] is already a bound, so kind annotations need a syntax of their own, which is to be decided.

Crates: boltlang-parser, boltlang-hir-def, boltlang-hir-ty.

Dominant language
Rust
Stars
54
Forks
3
Avg merge
7m
Merged PRs (30d)
29

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from boltlang/Bolt

All issues in boltlang/Bolt

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.