The history configuration was refactored in pry/pry@e5556a2

This makes most (if not all) of the Wiki page on history configuration out of date. Unfortunately, I don't have time right now to go through and figure out how all the options have changed, but perhaps someone more well-versed in the

Binding C++ and JavaScript — WebIDL Binder and Embind
https://emscripten.org/docs/porting/connecting_cpp_and_javascript/Interacting-with-code.html#binding-c-and-javascript-webidl-binder-and-embind

// quick_example.cpp
#include <emscripten/bind.h>

using namespace emscripten;

float lerp(float a,

See https://github.com/Neargye/magic_enum#readme.

If someone tries both Better Enums and magic_enum, and there is a reason to prefer Better Enums, please leave a comment here.

Otherwise, I think we should recommend magic_enum and move Better Enums toward deprecation.

cc @Neargye

Add API nameof::cstring to https://github.com/Neargye/nameof/blob/master/doc/reference.md

I have a table document with a column type of type document_type:

CREATE TYPE document_type AS ENUM (
    'NOTE',
    'PAGE'
);
CREATE TABLE document (
    id uuid NOT NULL,
    document_type document_type NOT NULL
);

This causes a name conflict in the generate types:

export type document_type = "NOTE" | "PAGE";

// ...

export namespace documentFields

Docs for user data. Add example test.

As documented in #134, type inference based on documented types is weak.

In practice, we want to detect type variance changes for complex types, such as @var Foo<Bar, Baz>.

We also want to detect changes such as:

function foo() {
-    return 1;
+    return 'foo';
}

These types are currently not inferred (BC check completely skipped), and that is a problem.

I think