Sharlock93

the amount of people who don't differentiate between cookin and cooking is too high, ofc that is just around me

I have been deep frying, shallow frying chicken a lot more recently, schnitzel is very much one of the best ways to eat chicken

AI just sucks is what I'm also hearing. Shrimple As.

Sad. Can't wait for that bubble to explode. It won't be a regular burst.

:') does bsky have bug reports? Should definitely make some noise about it

Relax Socrates, it's a weeb game. (Joking ofc this is some peak shit, I missed your game threads.)

I'm :D only one thing is hitting V2 as far as I'm aware, unless you have extra special access.

I'm very excited for the redacted tbh very cool stuff.

Redacted lol

The ironic and bleak funny part of this is that he is essentially calling the conservatives men dumb and undereducated which tbh they won't understand because they are both evil and uneducated.

I have PS+ premium so these are just included for free~

This is just me playing games from childhood now that I know English

Arc The Lad, which sounds super British.

Nah bro looks at my polygons! PS2 era is back

I love everything about these photos, peak fashion and style.

And more error prone.

All together :D

I'll have you know that I know of compilers that are deprecating c++17

This is the correct take. A few people chose A internally. Very sad day :')

We had an internal convo about which one someone should pick:

A)
If(const char* x = func()) {...}

Or

B)
const char* x = func();
If(x != nullptr) {...}

What do y'all think?

you can look types by name. and allows dynamically type construction. Renaming because you wanna
rename "basic_string<char, char_traits<char>, allocator<char>>" as "std::string" so you can look up it up easier.
why during static init? No earthly idea. They didn't profile this code.

Using A which needs updating now.
Internal structure doesn't keep track of relationships to make the update a minimal set thus testing against a lot of types.

This is an optimization I thought of to reduce it further beyond 8 seconds. However I was needed in other parts of the system and tasks :)

The problem is as follows:
You have type A, and then type B which is a templated type that has A as one of the template arguments.

The system allows type renaming so if you rename A => AA, the system will go through every templated type and reconstruct the names because one of those types might be

I mean this is the way to do it. I'm fairly certain if I had the time and the desire the stuff is as working on can be constexpred, not even need static init.

lmao

Final update on this for a while, this is now down to 8 seconds. Final piece of the puzzle was doing a compare against size of string check before the real check. And replacing string Compare function by strncmp. Memcmp might also work but, 2:07 to 8 seconds is a win.

I do my best to use vim and compile on the command line, even go as far as use a plugin on vim for debugging and running code.
It's just not programmer friendly.

My main gripe is I cannot watch a variable without pulling hair out.

There are considerations to be made around context free and non-context free grammars that might impact performance but that do not imply a specific choice in syntax.
In either case, not my circus not my monkeys.

I do not understand what this means tbh again my point and what i understood from the previous statement is that "zig is awkward because it wants faster parsing" which implies if you want "non-awkward syntax" you will have a slow parser which is not as far as i know a correct statement.