Introducing @vite.dev-plugin-compile-time v0.4
Call `compileTime` anywhere and it will be replaced with the returned data at compile time
git.new/compile-time
Call `compileTime` anywhere and it will be replaced with the returned data at compile time
git.new/compile-time
December 22, 2024 at 5:55 PM
Introducing @vite.dev-plugin-compile-time v0.4
Call `compileTime` anywhere and it will be replaced with the returned data at compile time
git.new/compile-time
Call `compileTime` anywhere and it will be replaced with the returned data at compile time
git.new/compile-time
I used the typestate pattern for the first time, converting runtime checks into compiletime ones. github.com/KittyCAD/ezp...
Enforce GeometryVariables invariants at type level by adamchalmers · Pull Request #102 · KittyCAD/ezpz
The GeometryVariables struct stores scalar variables that correspond to 2D points, or radii, or other geometric properties. It stores them in a flat 1D array. In order to properly map geometry back...
github.com
October 1, 2025 at 11:16 AM
I used the typestate pattern for the first time, converting runtime checks into compiletime ones. github.com/KittyCAD/ezp...
Unity: ‘Compiling scripts.’ Me: Goes for a coffee, contemplates life choices, returns to check progr#Unity3Dt#compiletimet#indiedevedev
November 9, 2024 at 7:30 PM
Unity: ‘Compiling scripts.’ Me: Goes for a coffee, contemplates life choices, returns to check progr#Unity3Dt#compiletimet#indiedevedev
kinda prefer prog langs w stricter syntax bc debugging at runtime is annoying enough wo compiletime errors getting thrown in the mix
February 29, 2024 at 8:23 PM
kinda prefer prog langs w stricter syntax bc debugging at runtime is annoying enough wo compiletime errors getting thrown in the mix
ESPfuscate (0.4.2) for esp32 by AndreaDV01
➡️ https://github.com/AndreaDV01/ESPfuscate
ESP32 Sensitive Data Obfuscator
#ArduinoLibraries #ArduinoLibs #esp32Libraries
➡️ https://github.com/AndreaDV01/ESPfuscate
ESP32 Sensitive Data Obfuscator
#ArduinoLibraries #ArduinoLibs #esp32Libraries
GitHub - AndreaDV01/ESPfuscate: CompileTime and RunTime plain text obfuscation for all ESP32 families
CompileTime and RunTime plain text obfuscation for all ESP32 families - AndreaDV01/ESPfuscate
github.com
April 30, 2026 at 5:30 PM
ESPfuscate (0.4.2) for esp32 by AndreaDV01
➡️ https://github.com/AndreaDV01/ESPfuscate
ESP32 Sensitive Data Obfuscator
#ArduinoLibraries #ArduinoLibs #esp32Libraries
➡️ https://github.com/AndreaDV01/ESPfuscate
ESP32 Sensitive Data Obfuscator
#ArduinoLibraries #ArduinoLibs #esp32Libraries
Java is catching up, but it’s still not there. Or: what #Scala has to offer for #Java devs?
By Paweł Stawicki: softwaremill.com/what-scala-h...
By Paweł Stawicki: softwaremill.com/what-scala-h...
What Scala has to offer for Java devs | SoftwareMill
Discover how Scala goes beyond to offer powerful features like type safety, implicit parameters, and compiletime insights, transforming your development on the JVM.
softwaremill.com
January 9, 2025 at 1:16 PM
Java is catching up, but it’s still not there. Or: what #Scala has to offer for #Java devs?
By Paweł Stawicki: softwaremill.com/what-scala-h...
By Paweł Stawicki: softwaremill.com/what-scala-h...
me: “I’ll just make a quick change and rerun it.”
rustc: “A quick what now?”
[10 minutes later]
me: sipping coffee, watching rustc like it’s a sourdough starter...
#rustlang #programminghumor #devmemes #rustacean #compiletime #softwareengineering #rustdev #developerlife #techhumor #rustc
rustc: “A quick what now?”
[10 minutes later]
me: sipping coffee, watching rustc like it’s a sourdough starter...
#rustlang #programminghumor #devmemes #rustacean #compiletime #softwareengineering #rustdev #developerlife #techhumor #rustc
August 5, 2025 at 11:14 AM
me: “I’ll just make a quick change and rerun it.”
rustc: “A quick what now?”
[10 minutes later]
me: sipping coffee, watching rustc like it’s a sourdough starter...
#rustlang #programminghumor #devmemes #rustacean #compiletime #softwareengineering #rustdev #developerlife #techhumor #rustc
rustc: “A quick what now?”
[10 minutes later]
me: sipping coffee, watching rustc like it’s a sourdough starter...
#rustlang #programminghumor #devmemes #rustacean #compiletime #softwareengineering #rustdev #developerlife #techhumor #rustc
When you use clang plugins to toy around because normal clang compiletime is just too slow ... Who had 5-10m iteration?
December 3, 2024 at 7:45 AM
When you use clang plugins to toy around because normal clang compiletime is just too slow ... Who had 5-10m iteration?
even python and typescript and lua and so on handle it better because their type checking is done strictly at loadtime, meanwhile godot's types are a cursed hybrid that try their best to do compiletime checks but ultimately can still throw a runtime error if you return the wrong type
August 12, 2026 at 11:02 AM
even python and typescript and lua and so on handle it better because their type checking is done strictly at loadtime, meanwhile godot's types are a cursed hybrid that try their best to do compiletime checks but ultimately can still throw a runtime error if you return the wrong type
Made a simple #StructOfArrays template library for #C++ leveraging #CompileTime #Reflection 🪞
- soa works for pretty much any struct type
- API similar to std::vector
- Access fields by name with soa.get<"...">
- Header-only
👉 github.com/gilzoide/soa...
#gamedev #indiedev #indiegamedev #C++20
- soa
- API similar to std::vector
- Access fields by name with soa.get<"...">
- Header-only
👉 github.com/gilzoide/soa...
#gamedev #indiedev #indiegamedev #C++20
GitHub - gilzoide/soa.hpp: Struct of Arrays (SoA) container template for C++20 that uses compile-time reflection to iterate over existing fields and access fields by name.
Struct of Arrays (SoA) container template for C++20 that uses compile-time reflection to iterate over existing fields and access fields by name. - gilzoide/soa.hpp
github.com
November 15, 2025 at 4:36 PM
Made a simple #StructOfArrays template library for #C++ leveraging #CompileTime #Reflection 🪞
- soa works for pretty much any struct type
- API similar to std::vector
- Access fields by name with soa.get<"...">
- Header-only
👉 github.com/gilzoide/soa...
#gamedev #indiedev #indiegamedev #C++20
- soa
- API similar to std::vector
- Access fields by name with soa.get<"...">
- Header-only
👉 github.com/gilzoide/soa...
#gamedev #indiedev #indiegamedev #C++20
At last year’s EuroRust, Tris took a deep-dive into const, macros, zero-cost abstractions, safety and how to offload huge amounts of computation from runtime to compiletime. Have a look as preparation for this year’s spooky game show! 🦀
📺 www.youtube.com/watch?v=McuK...
#RustLang #EuroRust26
📺 www.youtube.com/watch?v=McuK...
#RustLang #EuroRust26
Misusing Const for Fn and Profit - Tristram Oaten | EuroRust 2025
*Misusing Const for Fn and Profit - Tristram Oaten at EuroRust 2025 🦀*
Rust has a secret world that is inaccessible in most other languages. We call this shadowy land “Compile Time”, and you can do…
www.youtube.com
July 23, 2026 at 1:42 PM
At last year’s EuroRust, Tris took a deep-dive into const, macros, zero-cost abstractions, safety and how to offload huge amounts of computation from runtime to compiletime. Have a look as preparation for this year’s spooky game show! 🦀
📺 www.youtube.com/watch?v=McuK...
#RustLang #EuroRust26
📺 www.youtube.com/watch?v=McuK...
#RustLang #EuroRust26
Really nice ~3x performance improvement for String::push - and String::insert technically - when char::len_utf8 > 1 and the len is unknown at compiletime, all by avoiding memcpy.
github.com/rust-lang/ru...
github.com/rust-lang/ru...
speed up `String::push` and `String::insert` by lincot · Pull Request #124810 · rust-lang/rust
Addresses the concerns described in #116235.
The performance gain comes mainly from avoiding temporary buffers.
Complex pattern matching in encode_utf8 (introduced in #67569) has been simplified to...
github.com
April 10, 2025 at 2:02 AM
Really nice ~3x performance improvement for String::push - and String::insert technically - when char::len_utf8 > 1 and the len is unknown at compiletime, all by avoiding memcpy.
github.com/rust-lang/ru...
github.com/rust-lang/ru...
Fiz uma biblioteca de #StructOfArrays simples em #C++ usando #CompileTime #Reflection 🪞
- soa funciona pra basicamente qualquer tipo struct
- API similar a std::vector
- Accesse campos por nome com soa.get<"...">
- Header-only
👉 github.com/gilzoide/soa...
#gamedev #indiedev #indiegamedev #C++20
- soa
- API similar a std::vector
- Accesse campos por nome com soa.get<"...">
- Header-only
👉 github.com/gilzoide/soa...
#gamedev #indiedev #indiegamedev #C++20
GitHub - gilzoide/soa.hpp: Struct of Arrays (SoA) container template for C++20 that uses compile-time reflection to iterate over existing fields and access fields by name.
Struct of Arrays (SoA) container template for C++20 that uses compile-time reflection to iterate over existing fields and access fields by name. - gilzoide/soa.hpp
github.com
November 15, 2025 at 4:37 PM
Fiz uma biblioteca de #StructOfArrays simples em #C++ usando #CompileTime #Reflection 🪞
- soa funciona pra basicamente qualquer tipo struct
- API similar a std::vector
- Accesse campos por nome com soa.get<"...">
- Header-only
👉 github.com/gilzoide/soa...
#gamedev #indiedev #indiegamedev #C++20
- soa
- API similar a std::vector
- Accesse campos por nome com soa.get<"...">
- Header-only
👉 github.com/gilzoide/soa...
#gamedev #indiedev #indiegamedev #C++20
É, uma combinação disso, com certeza. No mundo Spring Boot / reflection+runtime um foco em Leyden + Native Image. No mundo Jakarta/Quarkus/Hibernate, um foco mais em annotation-processors+compiletime também se beneficiando com Leyden + NI, só que partindo de outro ponto inicial e pressuposto.
January 6, 2025 at 8:44 PM
É, uma combinação disso, com certeza. No mundo Spring Boot / reflection+runtime um foco em Leyden + Native Image. No mundo Jakarta/Quarkus/Hibernate, um foco mais em annotation-processors+compiletime também se beneficiando com Leyden + NI, só que partindo de outro ponto inicial e pressuposto.
Would refer to it as a conversion more than a cast but yes. Because the constructor is constexpr and it’s being fed with a float literal it even does this conversion at compiletime
November 6, 2025 at 1:36 AM
Would refer to it as a conversion more than a cast but yes. Because the constructor is constexpr and it’s being fed with a float literal it even does this conversion at compiletime
actually yes; Typescript's typesystem allows typing based on properties of numbers, so it can precalculate Fizzbuzz at compiletime
June 22, 2023 at 6:59 PM
actually yes; Typescript's typesystem allows typing based on properties of numbers, so it can precalculate Fizzbuzz at compiletime
docs.rs/schemars/lat... is a compiletime schema generator, but its corresponding runtime representation can be worked with; I don't think it makes any affordances for that, but you should be able to make it work if you don't find a better option
schemars - Rust
Schemars
docs.rs
February 11, 2025 at 6:34 PM
docs.rs/schemars/lat... is a compiletime schema generator, but its corresponding runtime representation can be worked with; I don't think it makes any affordances for that, but you should be able to make it work if you don't find a better option
ahh
i wonder if there could be a way to have a mutable field reference to an immutable structure, checked at compiletime... like "you're allowed to modify the individual elements, you just aren't allowed to modify their *container*
i wonder if there could be a way to have a mutable field reference to an immutable structure, checked at compiletime... like "you're allowed to modify the individual elements, you just aren't allowed to modify their *container*
January 30, 2025 at 1:14 AM
ahh
i wonder if there could be a way to have a mutable field reference to an immutable structure, checked at compiletime... like "you're allowed to modify the individual elements, you just aren't allowed to modify their *container*
i wonder if there could be a way to have a mutable field reference to an immutable structure, checked at compiletime... like "you're allowed to modify the individual elements, you just aren't allowed to modify their *container*
go users, is there any way to change stuff at compiletime, maybe based on flags passed to go run/build?
something like
//env: dev
abc := 42
//env: prod
abc := 2
So in prod abc will be 2 but while developing abc will be 42
#golang
something like
//env: dev
abc := 42
//env: prod
abc := 2
So in prod abc will be 2 but while developing abc will be 42
#golang
November 27, 2024 at 11:15 AM
go users, is there any way to change stuff at compiletime, maybe based on flags passed to go run/build?
something like
//env: dev
abc := 42
//env: prod
abc := 2
So in prod abc will be 2 but while developing abc will be 42
#golang
something like
//env: dev
abc := 42
//env: prod
abc := 2
So in prod abc will be 2 but while developing abc will be 42
#golang
and yeah I know multiple mutable references are bad but like... is there *some way* I can have a structure "remember" some piece of memory it was referencing mutably while giving someone else "a turn", with a compiletime guarantee the mutability is not given back until "their turn" ends?
January 29, 2025 at 6:37 PM
and yeah I know multiple mutable references are bad but like... is there *some way* I can have a structure "remember" some piece of memory it was referencing mutably while giving someone else "a turn", with a compiletime guarantee the mutability is not given back until "their turn" ends?
As in, I wish I could encode something like "this is integer is a key of this static hashmap" at compiletime so that I could look it up in the hashmap without needing to handle the possible key-is-missing failure. But afaik that's not possible. So checking upon deserialization like this is what I do
April 22, 2025 at 1:00 AM
As in, I wish I could encode something like "this is integer is a key of this static hashmap" at compiletime so that I could look it up in the hashmap without needing to handle the possible key-is-missing failure. But afaik that's not possible. So checking upon deserialization like this is what I do
In JavaScript, it can't be 'anytime' - because it can't be 'compiletime' 😆 OH YEAH!
Anyway: Your reasoning -> rules: ;)
"If an element of type T is added to our element e,
Then e also has type T"
or
"If we know that an element e is in an array, and that has type T,
Then e also has type T"
Anyway: Your reasoning -> rules: ;)
"If an element of type T is added to our element e,
Then e also has type T"
or
"If we know that an element e is in an array, and that has type T,
Then e also has type T"
August 21, 2025 at 12:32 PM
In JavaScript, it can't be 'anytime' - because it can't be 'compiletime' 😆 OH YEAH!
Anyway: Your reasoning -> rules: ;)
"If an element of type T is added to our element e,
Then e also has type T"
or
"If we know that an element e is in an array, and that has type T,
Then e also has type T"
Anyway: Your reasoning -> rules: ;)
"If an element of type T is added to our element e,
Then e also has type T"
or
"If we know that an element e is in an array, and that has type T,
Then e also has type T"