caoimhe
@caoimhe.dev
hi, i'm caoimhe! (she/her), i do a lot of things, maybe they'll be interesting enough to put here someday
💻 github.com/caoimhebyrne
🎵 last.fm/user/caoimhereal
🏳️🌈 🇮🇪
💻 github.com/caoimhebyrne
🎵 last.fm/user/caoimhereal
🏳️🌈 🇮🇪
Reposted by caoimhe
Have you visited Midport Village yet? 🤔
March 26, 2025 at 9:35 PM
Have you visited Midport Village yet? 🤔
one click join is now on modrinth!
this is a minecraft mod that allows you to join your last minecraft server through a button on the main menu!
modrinth.com/mod/one-clic...
this is a minecraft mod that allows you to join your last minecraft server through a button on the main menu!
modrinth.com/mod/one-clic...
March 25, 2025 at 4:02 PM
one click join is now on modrinth!
this is a minecraft mod that allows you to join your last minecraft server through a button on the main menu!
modrinth.com/mod/one-clic...
this is a minecraft mod that allows you to join your last minecraft server through a button on the main menu!
modrinth.com/mod/one-clic...
Reposted by caoimhe
your outie uses git checkout -b rather than git switch -c
February 18, 2025 at 5:58 PM
your outie uses git checkout -b rather than git switch -c
haven't posted a petal update in a while!
i've been busy with other stuff, but it is at a stage where we have almost-parity with what it was like before i started the refactor.
today i implemented references again, which are working a little bit better than before!
(1/2)
i've been busy with other stuff, but it is at a stage where we have almost-parity with what it was like before i started the refactor.
today i implemented references again, which are working a little bit better than before!
(1/2)
January 18, 2025 at 9:53 PM
haven't posted a petal update in a while!
i've been busy with other stuff, but it is at a stage where we have almost-parity with what it was like before i started the refactor.
today i implemented references again, which are working a little bit better than before!
(1/2)
i've been busy with other stuff, but it is at a stage where we have almost-parity with what it was like before i started the refactor.
today i implemented references again, which are working a little bit better than before!
(1/2)
another intellij update means another feature breaking (it's git this time)
January 17, 2025 at 1:52 PM
another intellij update means another feature breaking (it's git this time)
Reposted by caoimhe
Reposted by caoimhe
Hello, World! 🌍
IntelliJ IDEA is now on Bluesky. We’re here to share coding tips, provide updates, and stay connected with you.
📢 Follow us, tag your dev friends, and help spread the word!
IntelliJ IDEA is now on Bluesky. We’re here to share coding tips, provide updates, and stay connected with you.
📢 Follow us, tag your dev friends, and help spread the word!
January 10, 2025 at 10:28 AM
Hello, World! 🌍
IntelliJ IDEA is now on Bluesky. We’re here to share coding tips, provide updates, and stay connected with you.
📢 Follow us, tag your dev friends, and help spread the word!
IntelliJ IDEA is now on Bluesky. We’re here to share coding tips, provide updates, and stay connected with you.
📢 Follow us, tag your dev friends, and help spread the word!
today in petal:
we did a live stream on twitch! the refactor is going well :) a few things were implemented, most importantly though: diagnostics got a refresh! ^^
we did a live stream on twitch! the refactor is going well :) a few things were implemented, most importantly though: diagnostics got a refresh! ^^
January 4, 2025 at 8:21 PM
today in petal:
we did a live stream on twitch! the refactor is going well :) a few things were implemented, most importantly though: diagnostics got a refresh! ^^
we did a live stream on twitch! the refactor is going well :) a few things were implemented, most importantly though: diagnostics got a refresh! ^^
petal now has imports! i'd like to write an entire post about this, but i'll leave that until tomorrow.
i have a lot of code to clean up from the last few days of building 💤
i have a lot of code to clean up from the last few days of building 💤
December 31, 2024 at 11:04 PM
petal now has imports! i'd like to write an entire post about this, but i'll leave that until tomorrow.
i have a lot of code to clean up from the last few days of building 💤
i have a lot of code to clean up from the last few days of building 💤
new in petal: optionals!
variables previously had to be initialized with a value, but if your variable may not have a value, prefixing it with `?` tells the compiler that it may be null.
(1/3)
variables previously had to be initialized with a value, but if your variable may not have a value, prefixing it with `?` tells the compiler that it may be null.
(1/3)
December 31, 2024 at 4:30 PM
new in petal: optionals!
variables previously had to be initialized with a value, but if your variable may not have a value, prefixing it with `?` tells the compiler that it may be null.
(1/3)
variables previously had to be initialized with a value, but if your variable may not have a value, prefixing it with `?` tells the compiler that it may be null.
(1/3)
i've never gotten this far with a programming language project before! almost 100 commits over the last week ^^
i said to myself that i'd try to overcome any challenges i meet instead of just giving up. sticking to that has pushed me to go further than before! :)
github.com/caoimhebyrne...
i said to myself that i'd try to overcome any challenges i meet instead of just giving up. sticking to that has pushed me to go further than before! :)
github.com/caoimhebyrne...
December 30, 2024 at 5:54 PM
i've never gotten this far with a programming language project before! almost 100 commits over the last week ^^
i said to myself that i'd try to overcome any challenges i meet instead of just giving up. sticking to that has pushed me to go further than before! :)
github.com/caoimhebyrne...
i said to myself that i'd try to overcome any challenges i meet instead of just giving up. sticking to that has pushed me to go further than before! :)
github.com/caoimhebyrne...
also new in petal today: passing values by reference!
this was a bit easier than i thought, i'm still a little unsure of the syntax, but it'll do for now :)
this was a bit easier than i thought, i'm still a little unsure of the syntax, but it'll do for now :)
December 30, 2024 at 5:44 PM
also new in petal today: passing values by reference!
this was a bit easier than i thought, i'm still a little unsure of the syntax, but it'll do for now :)
this was a bit easier than i thought, i'm still a little unsure of the syntax, but it'll do for now :)
new in petal: type aliasing!
this required a refactor of the type system. the AST now generates unresolved types, which the typechecker now resolves and verifies before code-generation.
the `type` keyword will also be used for some cool stuff in the future ^^
this required a refactor of the type system. the AST now generates unresolved types, which the typechecker now resolves and verifies before code-generation.
the `type` keyword will also be used for some cool stuff in the future ^^
December 30, 2024 at 1:27 PM
new in petal: type aliasing!
this required a refactor of the type system. the AST now generates unresolved types, which the typechecker now resolves and verifies before code-generation.
the `type` keyword will also be used for some cool stuff in the future ^^
this required a refactor of the type system. the AST now generates unresolved types, which the typechecker now resolves and verifies before code-generation.
the `type` keyword will also be used for some cool stuff in the future ^^
Reposted by caoimhe
that actually turned out to be a way better idea!
as you can see by the screenshot, it now verifies types for number literals in variable declarations, and coerces them if it can safely do so!
it should be pretty trivial to expand this typechecking to function call arguments
as you can see by the screenshot, it now verifies types for number literals in variable declarations, and coerces them if it can safely do so!
it should be pretty trivial to expand this typechecking to function call arguments
December 29, 2024 at 8:05 PM
that actually turned out to be a way better idea!
as you can see by the screenshot, it now verifies types for number literals in variable declarations, and coerces them if it can safely do so!
it should be pretty trivial to expand this typechecking to function call arguments
as you can see by the screenshot, it now verifies types for number literals in variable declarations, and coerces them if it can safely do so!
it should be pretty trivial to expand this typechecking to function call arguments
all of this has me considering a different way to implement this though!
right now, it kinda just passes expected types around between functions when generating the code, but that also means that i have to figure all of that out *again* if i want to write another code generator. (1/3)
right now, it kinda just passes expected types around between functions when generating the code, but that also means that i have to figure all of that out *again* if i want to write another code generator. (1/3)
today in petal:
number literals are now generated with their expected type, instead of just `i32`. this currently only applies to variable declarations + binary operations, since it's a bit more work to make this apply to return statements & function parameters!
number literals are now generated with their expected type, instead of just `i32`. this currently only applies to variable declarations + binary operations, since it's a bit more work to make this apply to return statements & function parameters!
December 29, 2024 at 7:01 PM
all of this has me considering a different way to implement this though!
right now, it kinda just passes expected types around between functions when generating the code, but that also means that i have to figure all of that out *again* if i want to write another code generator. (1/3)
right now, it kinda just passes expected types around between functions when generating the code, but that also means that i have to figure all of that out *again* if i want to write another code generator. (1/3)
today in petal:
number literals are now generated with their expected type, instead of just `i32`. this currently only applies to variable declarations + binary operations, since it's a bit more work to make this apply to return statements & function parameters!
number literals are now generated with their expected type, instead of just `i32`. this currently only applies to variable declarations + binary operations, since it's a bit more work to make this apply to return statements & function parameters!
December 29, 2024 at 6:56 PM
today in petal:
number literals are now generated with their expected type, instead of just `i32`. this currently only applies to variable declarations + binary operations, since it's a bit more work to make this apply to return statements & function parameters!
number literals are now generated with their expected type, instead of just `i32`. this currently only applies to variable declarations + binary operations, since it's a bit more work to make this apply to return statements & function parameters!
clearly way too excited to spell "have" properly
the fact that i can use LLVM's C api to build LLVM modules from my own language is crazy!!!
the compiler for the language is written in C, and produces binaries using LLVM. the goal is to get to a stage where i can re-write the compiler in itself.
still haev a lot of work to do!
the compiler for the language is written in C, and produces binaries using LLVM. the goal is to get to a stage where i can re-write the compiler in itself.
still haev a lot of work to do!
December 26, 2024 at 10:56 PM
clearly way too excited to spell "have" properly
that was a lot of effort but i think it was worth it?
December 26, 2024 at 1:56 PM
that was a lot of effort but i think it was worth it?