1
ok no, i currently have no project to host there
GetViewportSize
m_vpAll prefixes and stuff
&mut&mut Nullable<> template. any pointer not in a Nullable must be non-null
but anyway, in cpp there is no diff between mut and const anyway in the call, also not for pointers
but anyway, in cpp there is no diff between mut and const anyway in the call, also not for pointers 
if statements TextEx function is also called in other places like the scoreboard, which does not cause this issueTextEx function is also called in other places like the scoreboard, which does not cause this issue 
QuadContainerAddQuads causes TextContainer.m_StringInfo.m_SelectionQuadContainerIndex = Graphics()->CreateQuadContainer(false); and it's happening even that I just opened console is it fine ? m_Elements.erase(...) in backend_vulkan.cpp?m_Elements.erase(...) in backend_vulkan.cpp? watch -n 0.1 'sudo pmap -x 78543 | grep "gesamt"'
where 78543 is my pid of DDNet 
1
char aBuf[128];
CImageInfo Info;
str_format(aBuf, sizeof(aBuf), "/path/to/file.png");
Graphics()->LoadPNG(&Info, aBuf, IStorage::TYPE_ABSOLUTE);
auto Handle = Graphics()->LoadTextureRaw(Info.m_Width, Info.m_Height, Info.m_Format, Info.m_pData, 0);
Graphics()->TextureSet(Handle);
Graphics()->QuadsBegin();
Graphics()->DrawRectExt(100, 100, 100, 100, 0, 0);
Graphics()->QuadsEnd(); LoadPNG every frame, but you do you! :D
2
std::string_view is such a meh abstraction over strings, not guaranteeing null termination was such a bad idea, it's basically completely useless for interoperability with any already existing code std::string_view is such a meh abstraction over strings, not guaranteeing null termination was such a bad idea, it's basically completely useless for interoperability with any already existing code 
open(2)open(2) open(2) 
O(n) strlen in Rust too
O(n) strlen in Rust too O(n) for one type of string and O(1) for the other. If you don't need strlen for your "operation" it's not a cost you pay 
1 1
strlen vectorized, and after that it's equivalent to whatever you'd do with length prefixed stringsstrlen vectorized, and after that it's equivalent to whatever you'd do with length prefixed strings 
1
/dev/fb0? @Jupstar ✪ 
♂️
>>> 1.0/0.0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ZeroDivisionError: float division by zero
not really bro, not really 1./sysdeps/x86_64/multiarch/strcpy-sse2.S I looked at the sse2 one./sysdeps/x86_64/multiarch/strcpy-sse2.S I looked at the sse2 one 
\0 is technically free game. e.g. strlens implementation knows nothing about the object size limits
