Trans health 

Trans health 

@rixx , Well, if I was looking *for* good. I still found it πŸ˜„

Yeah, I re-read it and actually thought about why it wasnt some form of "sehen", then checked the dictionary.

Thank you for your patience!

@rixx ( Zero confidence on "Suchen" being the word for "looking", as in "Looking good". Dictionaries vs translators, ugh sorry )

Pocket reminding me of my bad habit: Saving articles and never reading them.

To find a key word, its just a matter of consuming regular characters until a symbol/whitespace is encountered.

And then checking if the resulting sting is in the set of keys for the map of keyword tokens.

Much better than having to switch-case every single keyword.

Its a nice feeling to be able to write a commit message:
"Support all keywords in C99" for a compiler.

Its only able to tokenize all the keywords, but I think next week I'll be ready to parse something.
The lexer is pretty much done, bar a few tokens like quotes, full stops and the doubled up operators ( like &&, >> || etc ).

Its a fairly small commit thanks to all the effort I put in on making a compile time map of strings to object factory functions.

@breakthesystem Ich liebe der Politik in The Expanse.
Es macht der Welt mehr Mensch.

@breakthesystem The Expanse sind meine lieblingsbΓΌcher im Moment :D Die Fernseh Show auch!

Die einzige zu Star-Trek nahe bekommen im liebe.

I have really gotten lost in the universe, to the point where I would write fan-fic if I had the time.

In fact, the forum post I linked in the gist is a prime example:

dlang's runtime silently recreates associative arrays at runtime, even if it already created them at compile time. Because the backend of associative arrays is different for RT, and CT.

No warning, just sprinkle a few 'enum' and 'static' over things and maybe `assert(__ctfe)` and you might be able to force CTFE, or you'll get an error.

I really dislike how dlang uses keywords like 'enum' and 'static' to just...signal to the compiler that it could attempt CTFE.

Its frustrating that if the compiler doesnt manage to do CTFE, but CAN do runtime evaluation, it often just, doesnt tell you and does it at runtime.

If I'm trying to make this CTFE, I want to ENSURE that its CTFE, its hard to do that.

I've spent a few hours making a fancy compile-time snippet.

It allows one to give a super class, and generate an associative array of class name strings, to factory functions for getting an object of that class.
The associative array can be a compile-time constant.

Getting this to work properly, and understanding the, honestly, awful semantics of CTFE for dlang has been HARD.

Its for using in my lexer to make token objects from input strings.

Transphobia bullshit 

Trans, injections mention 

Trans, injections mention 

Trans, injections mention 

Trans, injections mention 

Anyway, I shall probably just pick something from that list tomorrow.

Today has mostly been building the chinch cage, but I have all evening for fun things!

Something I've been working on in therapy is being able to just decide what I want to do.

I often end up decision-paralysed because I want to do *so many things* and must pick the one most likely to result in enjoyment.
So, trying to pick the one that is least risky, in terms of being worth the time.

But I've been getting a lot better at just...feeling what I want to do and doing it, rather than assigning imaginary *worthwhileness* points to things I want to do.

Show more
Mastodon is one server in the network