Solype/Krc

Sign in to follow View on GitHub

Compiler for a Korean-syntax language, written in Rust: hand-written lexer, LR(1) parser, typed IR, and its own x86-64 encoder and ELF writer. Made for the Compiler class of CAU.

Is Solype/Krc beginner-friendly?

The maintainers of Solype/Krc usually reply to a pull request within 1 day. 2 beginner-friendly issues are open now.

Stars
1
Forks
1
Open beginner issues
2
Indexed issues
34
Avg merge
3h 10m
Merged PRs (30d)
16
Dominant language
Rust
License
MIT
Last GitHub push
Nov 2, 2026
Latest indexed
Nov 3, 2026
Contributing guide
No code of conduct
Beginner labels
good first issue

How to contribute to Solype/Krc

  1. Read the contributing guide first: it says how the maintainers want changes proposed, tested and reviewed.
  2. Your contributions will be published under the project's MIT license.
  3. Pick one of the 2 open beginner-friendly issues below and comment that you want to work on it before you start.
Beginner friendly Everything
Open All

Issues somebody may already be working on are listed last. List everything by date

  • Post-parser: 넣어서 is read as a call of a function 넣다
    Open
    • Is something wrong?
    bug front-end

    Difficulty 2/5 1-3 hours Newbie friendliness 78/100

    Solype/Krc#50 ·

    Maintainers usually reply within 1 day

  • Post-parser: a leading NAME에 is not given to 넣어요
    Open
    • Is something wrong?
    bug front-end

    Difficulty 2/5 1-3 hours Newbie friendliness 75/100

    Solype/Krc#49 ·

    Maintainers usually reply within 1 day

  • Backend: instructions and registers not needed by the compiler
    Open
    • Is something wrong?
    backend later

    Difficulty 5/5 Over a week Newbie friendliness 8/100

    Solype/Krc#31 ·

    Maintainers usually reply within 1 day

  • Backend: shorter encodings
    Open
    • Is something wrong?
    backend later

    Difficulty 3/5 Half a day Newbie friendliness 55/100

    Solype/Krc#30 ·

    Maintainers usually reply within 1 day

  • Backend: short jumps (rel8)
    Open
    • Is something wrong?
    backend good first issue later

    Difficulty 4/5 3-5 days Newbie friendliness 30/100

    Solype/Krc#29 ·

    Maintainers usually reply within 1 day

  • Backend: encoder test tooling
    Open
    • Is something wrong?
    backend tooling

    Difficulty 3/5 1-2 days Newbie friendliness 45/100

    Solype/Krc#28 ·

    Maintainers usually reply within 1 day

  • Backend: API cleanups
    Open
    • Is something wrong?
    backend

    Difficulty 3/5 1-2 days Newbie friendliness 45/100

    Solype/Krc#27 ·

    Maintainers usually reply within 1 day

  • Backend: .bss without bytes in the file
    Open
    • Is something wrong?
    backend enhancement

    Difficulty 3/5 1-2 days Newbie friendliness 45/100

    Solype/Krc#26 ·

    Maintainers usually reply within 1 day

  • Backend: GOTPCREL relocation
    Open
    • Is something wrong?
    backend enhancement

    Difficulty 4/5 3-5 days Newbie friendliness 35/100

    Solype/Krc#25 ·

    Maintainers usually reply within 1 day

  • Samples: check the output of every sample
    Open
    • Is something wrong?
    enhancement good first issue tooling

    Difficulty 2/5 1-3 hours Newbie friendliness 62/100

    Solype/Krc#24 ·

    Maintainers usually reply within 1 day

  • Error messages: show the source line with ^
    Open
    • Is something wrong?
    front-end tooling

    Difficulty 3/5 1-2 days Newbie friendliness 62/100

    Solype/Krc#23 ·

    Maintainers usually reply within 1 day

  • Parser: report LR(1) conflicts and expected tokens
    Open
    • Is something wrong?
    front-end tooling

    Difficulty 3/5 1-2 days Newbie friendliness 50/100

    Solype/Krc#22 ·

    Maintainers usually reply within 1 day

  • Language: irregular verbs
    Open
    • Is something wrong?
    front-end later

    Difficulty 4/5 3-5 days Newbie friendliness 35/100

    Solype/Krc#21 ·

    Maintainers usually reply within 1 day

  • Language: unsigned 32-bit integer
    Open
    • Is something wrong?
    enhancement front-end

    Difficulty 3/5 Half a day Newbie friendliness 50/100

    Solype/Krc#20 ·

    Maintainers usually reply within 1 day

  • Parser: sentence declaration with parameters and no return
    Open
    • Is something wrong?
    enhancement front-end

    Difficulty 3/5 1-2 days Newbie friendliness 45/100

    Solype/Krc#19 ·

    Maintainers usually reply within 1 day

  • Pre-parser: check particles against the 받침
    Open
    • Is something wrong?
    enhancement front-end

    Difficulty 4/5 3-5 days Newbie friendliness 35/100

    Solype/Krc#17 ·

    Maintainers usually reply within 1 day

  • Converter: unit tests
    Open
    • Is something wrong?
    converter tooling

    Difficulty 3/5 Half a day Newbie friendliness 62/100

    Solype/Krc#16 ·

    Maintainers usually reply within 1 day

  • Converter: cleanups
    Open
    • Is something wrong?
    converter good first issue tooling

    Difficulty 3/5 1-2 days Newbie friendliness 45/100

    Solype/Krc#15 ·

    Maintainers usually reply within 1 day

  • Structures (구조) and Type::Custom
    Open
    • Is something wrong?
    converter front-end later

    Difficulty 5/5 Over a week Newbie friendliness 18/100

    Solype/Krc#14 ·

    Maintainers usually reply within 1 day

  • Converter: signature of main
    Open
    • Is something wrong?
    converter enhancement

    Difficulty 3/5 Half a day Newbie friendliness 48/100

    Solype/Krc#13 ·

    Maintainers usually reply within 1 day

  • Converter: variable read before it has a value
    Open
    • Is something wrong?
    converter enhancement

    Difficulty 3/5 1-2 days Newbie friendliness 42/100

    Solype/Krc#11 ·

    Maintainers usually reply within 1 day

  • Converter: warn about code after a return, 그만해요 or 넘어가요
    Open
    • Is something wrong?
    converter enhancement

    Difficulty 3/5 1-2 days Newbie friendliness 55/100

    Solype/Krc#10 ·

    Maintainers usually reply within 1 day

  • Converter: 참인 동안 with a return inside gives MissingReturn
    Open
    • Is something wrong?
    bug converter

    Difficulty 3/5 Half a day Newbie friendliness 62/100

    Solype/Krc#9 ·

    Maintainers usually reply within 1 day

  • Register allocation instead of stack slots
    Open
    • Is something wrong?
    codegen later

    Difficulty 5/5 Over a week Newbie friendliness 12/100

    Solype/Krc#8 ·

    Maintainers usually reply within 1 day

  • Converter: 바꾸다 as a statement alone
    Open
    • Is something wrong?
    bug converter good first issue

    Difficulty 2/5 1-3 hours Newbie friendliness 62/100

    Solype/Krc#7 ·

    Maintainers usually reply within 1 day

  • Pointers and arrays: Load, Store, AddrOf
    Open
    • Is something wrong?
    codegen converter enhancement

    Difficulty 4/5 3-5 days Newbie friendliness 25/100

    Solype/Krc#6 ·

    Maintainers usually reply within 1 day

  • Codegen: 7th integer argument and more on the stack
    Open
    • Is something wrong?
    codegen enhancement

    Difficulty 4/5 3-5 days Newbie friendliness 50/100

    Solype/Krc#5 ·

    Maintainers usually reply within 1 day

  • Codegen: casts from an unsigned value
    Open
    • Is something wrong?
    codegen enhancement

    Difficulty 3/5 1-2 days Newbie friendliness 62/100

    Solype/Krc#2 ·

    Maintainers usually reply within 1 day

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.