Pedant | fix bothersome punctuation and formatting errors

Don't call delete on an object you didn't allocate with new. This object will be deleted when it goes out of scope, so there's nothing special to do to destroy it properly.

When you want objects to start their lifetime inside a scope and end their lifetime when the scope ends, don't use new and delete. Just declare them normally.

Use new and delete for objects whose lifetimes you want to manage. Allocate them with new and call delete when you are done with them.

So they both still violate the rule that that structured bindings are never names of variables, making them never capturable?

No, it is actually clang that is violating the standard, at least for the compiler flags provided. In C++20, the restriction of not directly supporting captures of structured binding aliases has been lifted, allowing them to be directly used without falling back to constructs using init-captures:

Change [expr.prim.lambda.capture]p8 (7.5.5.2) as follows:

If a lambda-expression explicitly captures an entity that is not odr-usable or captures a structured binding (explicitly or implicitly) , the program is ill-formed.

This should work:

From css-tricks.com/specifics-on-css-specificity:

The universal selector (*) has no specificity value (0,0,0,0)

This is why the selector h1 from normalize is applied since it has a higher specificity of (0,0,0,1)

You could update your selector like the following to ensure it overrides normalize:

If you are giving up on overloads, but you still want a return type that switches depending on the parameter, then you will need to use a generic function returning a conditional type. For example:

The package neovim of your package manager provided the commands nvim (and possibly vim as well).

After removing the package via sudo apt remove neovim, those commands will be gone. Just by downloading a new version (outside the comfort of your package manager), you won't get a "command" installed. If you want to keep using this downloaded version, the easiest way to do so IMO would be to:

 1. Move or symlink the new executable to some new folder like ~/bin:

[special]/7:

For a class, its non-static data members, its non-virtual direct base classes, and, if the class is not abstract ([class.abstract]), its virtual base classes are called its potentially constructed subobjects.

[class.default.ctor]/2.7 says that a defaulted default constructor is defined as deleted if

any potentially constructed subobject, except for a non-static data member with a brace-or-equal-initializer, has class type M (or array thereof) and either M has no default constructor or overload resolution ([over.match]) as applied to find M's corresponding constructor results in an ambiguity or in a function that is deleted or inaccessible from the defaulted default constructor

So we can exclude virtual bases from the set of potentially constructed subobjects by making Proxy abstract, for instance by making the destructor pure virtual (but still supply a definition):

Well, you can define errors as an array, each index of Input is an element of the array.

https://codesandbox.io/s/youthful-cdn-83t35?file=/src/Input.jsx

When inserting a string to the tree, your code assumes that every prefix of that string has already been inserted. This mostly works because the strings are sorted by length.

However, the strings .-.-. and .-.-- are inserted to the tree while their prefix .-.- is never inserted. This causes a recursive call to tree_insert with root == NULL. I'm surprised this doesn't crash for you on Linux, as it did for me.

In your fixed code you removed the .-.-. and .-.-- strings so it works.