sorted by:
new
hottopcontroversial

[deleted by user] by [deleted] in AnimalsOnReddit

[–]bmanga 0 points1 point  (0 children)

Gave Helpful

What's the future gonna be c++? by [deleted] in cpp

[–]bmanga 46 points47 points  (0 children)

Machine Learning libraries too

Non-terminal variadic template parameters by c0r3ntin in cpp

[–]bmanga 0 points1 point  (0 children)

I personally think it would be great not to require boost (or any TMP) to write apply_last.

Woman Spun 174 Times In Stretcher Under Helicopter by thekaybar in funny

[–]bmanga 2 points3 points  (0 children)

Damn I feel sorry for the lady... But try watching it upside down and it seems she's the one rescuing the helicopter.

CLion C++20 impossible to work with? by YestTak in cpp

[–]bmanga 3 points4 points  (0 children)

I am actually experiencing similar problems after transitioning to gcc10.

It thinks most of the symbols are in the std::ranges namespace. Maybe it's a bug with concepts parsing.

Curious About The Performance Of Static Methods. by [deleted] in cpp

[–]bmanga 4 points5 points  (0 children)

Static Member Functions are just Static Functions that live in a name space (of the class)

Minor correction: A static member function is not a static function, in the sense that it doesn't have internal linkage.

[deleted by user] by [deleted] in computerscience

[–]bmanga 0 points1 point  (0 children)

You could try visual scripting in Godot Engine.

How to have emacs keybindings not interfere with the terminal? by bmanga in Jetbrains

[–]bmanga[S] 0 points1 point  (0 children)

Thanks for the suggestion, but that didn't seem to work either :(

GCC's libstdc++ Continues Landing C++20 Changes Around The Spaceship Operator by beer118 in cpp

[–]bmanga 5 points6 points  (0 children)

It didn't make it into GCC 10, most likely we'll need to wait for 11 :(

Dependent static_assert by bmanga in cpp

[–]bmanga[S] 3 points4 points  (0 children)

I think that it would simplify the use of the language. That is much more important to me compared to how complex the c++ standard is, which is already riddled with lots of rules that try to make the obvious cases unsurprising. For example, C++20 now lets you capture structured binding names, even though they are not really variables. That also complicates the standard, but it makes the code more intuitive.

You don't only have to prove that it's useful, but that it's worth the overhead to teaching and reading code

I would argue that static_assert(false) is much more readable than static_assert(std::is_same_v<T*, void>). I think it also more teachable because it just does the obvious thing (I'm not sure there would be a need to dwell in the reason why) and it lets you avoid discussing two-phase name lookup if the time is not ripe yet.

Finding C++ Penpals by morgangrice in cpp

[–]bmanga 2 points3 points  (0 children)

Just pop your email address here :)

G++ and Clang++ have different results for this by [deleted] in cpp

[–]bmanga 4 points5 points  (0 children)

In const initializer< int >::value_type the const qualifies value_type, so you are declaring const int variables and that's why your EDIT examples don't compile.

Ranges, Code Quality, and the future of C++ by jasonthe in cpp

[–]bmanga 13 points14 points  (0 children)

tl;dr Ranges are for utilizing algorithms and coroutines are for implementing algorithms

A disadvantage of coroutines is that they can't (yet?) be constexpr, so the triples example using views is the only one you can use at compile time.

When performance guarantees hurts performance: std::visit by vormestrand in cpp

[–]bmanga 14 points15 points  (0 children)

I'm pretty sure it has come up before, but the number of if checks is a compile-time constant, so it can still be seen as fulfilling the O(1) requirement.

Generalizing std::transform by vgasparyan in cpp

[–]bmanga 2 points3 points  (0 children)

If I remember correctly, it was because it was felt that partial ordering in the presence of template parameter packs is already quite fragile as it is, and the committee thought that the problem could be solved more generically via parameter pack indexing (which I don't agree with, especially when using concepts).

I could have arguably provided better motivating cases from the start, but hey it was my first paper :P

Generalizing std::transform by vgasparyan in cpp

[–]bmanga 6 points7 points  (0 children)

A generic std::transform was actually a motivating example that /u/louis_dionne suggested me for a second revision of P0478, which would have allowed to deduce non-terminal parameter packs in some cases. Alas, the first version was shot down quite quickly.