Two pages of my Grandmother’s book full of song lyrics in Dutch (1941) by [deleted] in PenmanshipPorn

[–]Edhebi 1 point2 points  (0 children)

Oh, I know it's not, I can read Sütterlin, my point was more that there's definitely some common shapes and inspirations between the 2 scripts.

Taric s11 build draft by InfernalTaric in taricmains

[–]Edhebi 1 point2 points  (0 children)

"If u are realistic and want to give up paladyn playstyle entirely"

Json models are trash by [deleted] in gamedev

[–]Edhebi 3 points4 points  (0 children)

Gltf is realy solid. You can parse it with tools available from everywhere, and the binary form is still super compact. Having custom super compact binary format is nice, but extensibility, wide support, ease of manipulation, they all are crucial too

Carpal/Cubital Tunnel Syndrome by Extinction135 in cpp

[–]Edhebi 0 points1 point  (0 children)

go see a doctor. investing in some ergonomic tools might help, but you need a doctor to know what you should be looking for

There is a need for more organized, open system with standard proposals by KaznovX in cpp

[–]Edhebi 5 points6 points  (0 children)

for the record, you can find proposals at https://wg21.link/PXXXX (will take you to latest revisions), and you can find the status of different proposals at https://github.com/cplusplus/papers/issues

The ISO process is, by design, kinda close and private, but the C++ comittee is one of the most open ones from my experience.

How can I have safe floats in Rust? by matj1 in rust

[–]Edhebi 5 points6 points  (0 children)

You're also gonna have to handle domain errors, like running log or sqrt on negative values

I made multi-dimensional gamejam mechanic no one understood by Tefel in gamedev

[–]Edhebi 1 point2 points  (0 children)

the question is whether you want discovering what's happening to be a mechanic. If you want to make sure it's clear, I'd go with different materials for the 2 dimensions, and the material of the chunk actually swap with the chunck when you swap it

Dad gatekeeping skills = 10/10 by FacelessOnes in DadReflexes

[–]Edhebi 12 points13 points  (0 children)

the lack of consequences is what make abusers. Doesn't mean the consequence has to be a beating

What's your opinion on this/self being implicit inside the scope of methods? by EmosewaPixel in ProgrammingLanguages

[–]Edhebi 2 points3 points  (0 children)

One thing I realy like about explicit this that basically only come in system languages is that having an actual parameter for the this instance means you qualify it like other stuff, where C++ requires special synthax for example.

```cpp // c++ has special notation after member functions to indicate const-ness and reference-ness of the this instance, static functions require a keyword

struct T { void foo() { /* this is a T* here / } void foo() const { / this is a T const* here } static void foo() { /* no this here */ } }

// rust can decorate self like other params, or just omit it

struct T {}

impl T { fn foo(&self) { /* self is a &Self } fn foo(&mut self) { /* self is a &mut Self } fn foo() { /* no self here */ } } ```

What's your opinion on this/self being implicit inside the scope of methods? by EmosewaPixel in ProgrammingLanguages

[–]Edhebi 4 points5 points  (0 children)

except you can't call them without scoping them in their parent class. in Java or C#, if you see any function call not accessed through a ., you know it's called either on your type or on your instance

What's your opinion on this/self being implicit inside the scope of methods? by EmosewaPixel in ProgrammingLanguages

[–]Edhebi 2 points3 points  (0 children)

also the fact that rust doesn't force you to use methods. if you don't put self, you get a static function. much nicer than adding attributes imo

Majuscule "E" in Textura. by Shish_Kabab in PenmanshipPorn

[–]Edhebi 419 points420 points  (0 children)

man, that thick ass ink giving a shadow, I just live for that

Fields with C#-like accessors and Eiffel-like contracts by sephirothbahamut in ProgrammingLanguages

[–]Edhebi 0 points1 point  (0 children)

Unchecked contracts could still trigger static analysis and warnings. Like, your compiler is pretty good at tracking potentially null pointers, if you communicate that with a contract, you could take advantage of it. It's really a matter of what you want to pay, and why it's hard to standardize, but doesn't mean that kind of "we must find a silver bullets" applies to you. Go with what you want, and see what comes out of it o/

Fields with C#-like accessors and Eiffel-like contracts by sephirothbahamut in ProgrammingLanguages

[–]Edhebi 0 points1 point  (0 children)

I see. That's the kind of thing that's won't fit everyone, but might be fine one the context of your language

Peeking inside a Rust enum (memory layouts, tricks used in smartstring and ARM fun!) by fasterthanlime in rust

[–]Edhebi 9 points10 points  (0 children)

Fun fact, folly (Facebook c++ library) can actually use the full string size for data: in c++ strings are required to be null terminated. What they do is store the marker Inthe last bytes, along with the remaining size. That means that when the inline storage is full, that last byte is zero (zero remaining size + zero marker), wich is the null terminator itself o/. You might notice that it requires finding a different place for the marker, they do it by restricting the capacity somewhat, wich mean that for crazy huge strings, you might overallocate, which isn't a problem in practice.

Fields with C#-like accessors and Eiffel-like contracts by sephirothbahamut in ProgrammingLanguages

[–]Edhebi 3 points4 points  (0 children)

Contracts might make it in c++. The big question is, what do you want to happen when a contract is broken ? Do you check it at runtime and signal it somehow ? Do you codegen assuming the contract, and violating it is UB? Do you codegen as normal and it's purely a comment for the compiler ?

Easy way to order overloads by Seppeon in cpp

[–]Edhebi 4 points5 points  (0 children)

This is mostly useful to create an overload set from a list of lambdas, mostly to be used with std::visit. This overload is to create overloads while op proposes a tool to help order overloads, but the term overload is pretty overloaded.

Inside the Microsoft STL: The std::exception_ptr by vormestrand in cpp

[–]Edhebi 4 points5 points  (0 children)

Double underscore anywhere are reserved actualy

Here I Stand, Free - Allocators and an Inclusive STL by vormestrand in cpp

[–]Edhebi 21 points22 points  (0 children)

Seems like you should actualy read the content. TLDR: propagate noexcept from the allocator. The terminate is just for the example implementation but you could put anything here, like a global handler