i work in robotics

i work in robotics

there you tend to try to minimize both memory and speed

i mean maximize speed

by not using std::string?

you literally cannot on a lot of things

and even then not the whole std library is ported

const string nl ="\n" would also help

Printf does suck too, it's better to use boost::format

You just wasted at least 24 bytes, when all you needed was 2 char nl[] = "\n"; Edit: I know @QNeko will try to be wiser

You just wasted at least 24 bytes, when all you needed was 2 char nl[] = "\n"; Edit: I know @QNeko will try to be wiser

You just wasted at least 24 bytes, when all you needed was 2 char nl[] = "\n"; Edit: I know @QNeko will try to be wiser

and you wasted many cache misses char nl ='\n';

and even wiser: template<class char_type> constexpr char_type nl() const { return '\n'; }

and even wiser: template<class char_type> constexpr char_type nl() const { return '\n'; }

cache misses?

cache misses?

How about fmt:: from https://github.com/fmtlib/fmt

Never heard of it. Seems cool though

Never heard of it. Seems cool though

you little shit xDD

you little shit xDD

CPU trying to query its cache of RAM and having to load RAM because data is not in cache

and even wiser: template<class char_type> constexpr char_type nl() const { return '\n'; }

I see

U don goofed m8

CPU cache, L1... L3 is faster than RAM

yea

did I again placed the constexpr wrong?

1. const only work inside struct | class 2. nl() is NOT that wise sire

1. const only work inside struct | class 2. nl() is NOT that wise sire

const works everywhere

/slap Even in main() ?

int main() const ?

but it should work

TRy that sire

allows for any char type to be used, even wchar_t

is it the linker or the compiler who complains?

Compiler

allows for any char type to be used, even wchar_t

CPU cache, L1... L3 is faster than RAM

We wouldn't need it if it was slower ^_^

and even wiser: template<class char_type> constexpr char_type nl() const { return '\n'; }

it seems much easier and does everything you want

Guys, you're descussing bullshit ^-^ \n is not that hard to type :D

You use exactly the word easy, and I will say, as opposed to simple from the compiler standpoint

i agree

You just wasted at least 24 bytes, when all you needed was 2 char nl[] = "\n"; Edit: I know @QNeko will try to be wiser

And you say functionnal programing is important, but you do not understand its value here

std::ostream& nl(std::ostream& cout) { return cout <<'\n'; } Usage: std::cout << "Line" << newl << "Text";

And you say functionnal programing is important, but you do not understand its value here

std::ostream& nl(std::ostream& cout) { return cout <<'\n'; } Usage: std::cout << "Line" << newl << "Text";

i was gonna propose a similar one

std::ostream& nl(std::ostream& cout) { return cout <<'\n'; } Usage: std::cout << "Line" << newl << "Text";

the issue here is you cast a char into a string

Issue closed

We value : Integration, Simplicity and principle of the least surprise

you do not have the right to close this issue for this repo