In stat.h was thinking ah nice lots if timestamps but two seem to be the same, modify and change, maybe one should be "create".
struct Stat {
Type type;
usize size;
SystemTime accessTime;
SystemTime modifyTime;
SystemTime changeTime;
In stat.h was thinking ah nice lots if timestamps but two seem to be the same, modify and change, maybe one should be "create".
struct Stat {
Type type;
usize size;
SystemTime accessTime;
SystemTime modifyTime;
SystemTime changeTime;
// This should be fine from a technical standpoint since the code
// don't care about the message, but the user does though.
Reminds me of when you should use modules:
"The project has no downstream users [...] or you just don't care about them anymore"
// This should be fine from a technical standpoint since the code
// don't care about the message, but the user does though.
Reminds me of when you should use modules:
"The project has no downstream users [...] or you just don't care about them anymore"
Really weird it's all so short. Still has json, markdown, svg is still only a circle I think but has bezier in math.
I like the _eatWhitespace function name.
It's very organised and very short for what it is. Almost cant really believe this is already enough
Really weird it's all so short. Still has json, markdown, svg is still only a circle I think but has bezier in math.
I like the _eatWhitespace function name.
It's very organised and very short for what it is. Almost cant really believe this is already enough
This Bluesky is very chronological and finite.
It feels a bit empty like when you've just made a new website. A weird lack of depth that everyone can feel but would be impossible to describe.
This Bluesky is very chronological and finite.
It feels a bit empty like when you've just made a new website. A weird lack of depth that everyone can feel but would be impossible to describe.
Really cool an OS in C++ must follow
Really cool an OS in C++ must follow