Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Defining a built-in operator has no effect

Open
#97 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
compilers

Research direction

Start by reading the boltlang-hir-ty crate and tracing how operator definitions are handled versus how built-in + expressions are resolved. Decide whether definitions should participate in resolution through a class such as Num or produce a diagnostic. Done means a definition has the chosen observable behavior, with a regression test covering it.

Written by the indexing model from the issue text.

Description

bug scope:types

Defining a built-in operator, like fn a + b, has no effect: + in expressions is still built in. Only other operators, like <>, call their definition.

Either such definitions should be used, through a class like Num, or they should be reported.

Crates: boltlang-hir-ty.

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

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.