cskartikey

Tagged your project as well cooked!

🔥 cskartikey marked your project as well cooked! As a prize for your nicely cooked project, look out for a bonus prize in the mail :)

SeradedStripes Commits Gizzy Fraud while cuddling his blahaj to death also meoww

Shipped this project!

Hours: 38.12
Cookies: 🍪 1105
Multiplier: 28.98 cookies/hr

V1.0.0 Release

  • Released version 1.0.0

Essentially this version is the final of the current compiler
If you read the repo you’ll see that another version is under way and its for low-level access. Once it is done I am going to rewrite proper Shiden in it.

SeradedStripes Commits Gizzy Fraud while cuddling his blahaj to death also meoww

Updates

  • Almost complete asm and rust compiler parity
  • Refactored repo a bunch by moving stuff around
  • Added shipwrights notice for rust version from when I shipped that (still pending 😭)
  • Also my changelog is too long to include in here due to character limit or word limit idk anymore

The attachments are the output of the examples/docs demo for linux

Next

  • Windows compiling in asm compiler
  • Updated vscode extension
  • Some libraries
  • Reimplementing the cli times
Attachment
Attachment
Attachment
0
SeradedStripes Commits Gizzy Fraud while cuddling his blahaj to death also meoww

Updates

  • After not cooking peak in asm, i decided im goign to rewrite everythin in asm

Changelog

Attachment
1

Comments

Rupnil
Rupnil 6 months ago

PEAK

SeradedStripes Commits Gizzy Fraud while cuddling his blahaj to death also meoww

Updates Windows Compiling works except for one single test. Im going to ignore that test exists

Changelog

Attachment
Attachment
0
SeradedStripes Commits Gizzy Fraud while cuddling his blahaj to death also meoww

Updates

  • Bunch of fixes
  • Added Todo section to readme
  • Tests should work
  • Fixed the whole language not having proper support for arrays and other stuff

What next?

  • a Static Translation Layer (~a lot of hours)
  • more libraries (~less hours but still alot)
  • Clear up warnings in rust code (~way less hours)
Attachment
0
SeradedStripes Commits Gizzy Fraud while cuddling his blahaj to death also meoww

Updates

  • Syntax & core: Lexer, recursive-descent parser, AST, and a tree-walk interpreter.
  • Types & values: i64, f64, char, string, array, unit, bool.
  • Expressions & operators:
    • Arithmetic: +, -, *, /.
    • Comparisons: ==, !=, <, <=, >, >=.
    • Logical: &&, ||, unary !.
    • Unary negation: -.
    • Indexing: a[index].
    • Function calls and arguments.
  • Statements & control flow:
    • let (with optional mut), assignments, return.
    • if / else, while, for <var> in <iterable>.
    • break, continue.
  • Collections & builtins:
    • Arrays and array operations: push, pop, len, range.
    • Builtins: println, print, file read_file/write_file (where available).
  • Additional details:
    • Typed terminators like /i64 or a plain / are used to end many statements and declarations.

Thats basically the whole language so far lol, but I have way to much warnings in my code, gonna focus on that and then im going to implement libraries like filesystem, windows, inputs, audios, ect.

Oh also I didnt not update the vscode extension yet
Also debugging took too long 💀
If hackatime extension recorded my terminal it would be way more hours as this is just a summary of everything ive done so far

The attachment is what vscode sees as problems, it probably didnt catch everything but its a crazy amount

Attachment
0