Implementation of enumify

[iK4tsu]

A core feature of Taurus lib. This new type enumify is similar to a dynamic enum. Basically an enum with types that can change at runtime. This is influenced by Rust's enums.

Basic usage:

import std.taurus.enumify;

// to define a new type
struct Option(T) {
	@Member!("Some", T)
	@Member!("None")
	mixin enumify;
}

Usage:

void main() {
	Option!int o = Option.Some(4);

	assert(o.match!(
		(Option!int.some) => true,
		(Option!int.none) => false
	));

	o = Option.None;

	assert(o.match!(
		(Option!int.some) => false,
		(Option!int.none) => true
	));
}

Types can created inside scopes must be static:

import std.taurus.enumify;

void main() @safe pure nothrow @nogc {
	static struct Option(T) {
		@Member!("Some", T)
		@Member!("None")
		mixin enumify;
	}

	Option!string o = Option.None;
}

This works with @nogc and BetterC!

Values can be accessed inside match.

static struct Option(T) {
	@Member!("Some", T)
	@Member!("None")
	mixin enumify;
}

Option!string o = Option.Some("foo");
	
o.match!(
	(Option!string.some s) { assert(s == "foo"); }
	(_) { assert(false); }
);

[ljmf00]

LGTM, but we need to fix the CI first, by updating the pinning version to the latest. Also, don't push personal branches on the upstream repository https://github.com/taurus-d/taurus/branches. Please use your fork instead.

[iK4tsu]

LGTM, but we need to fix the CI first, by updating the pinning version to the latest. Also, don't push personal branches on the upstream repository taurus-d/taurus/branches. Please use your fork instead.

I forgot to fork this repo. Do we merge this directly (after the CI fix), or do I make a new duplicated PR but from my fork?

[ljmf00]

On Thu, 2021-06-03 at 09:45 -0700, João Lourenço wrote: > LGTM, but we need to fix the CI first, by updating the pinning > version to the latest. Also, don't push personal branches on the > upstream repository taurus-d/taurus/branches. Please use your fork > instead. I forgot to fork this repo. Do we merge this directly (after the CI fix), or do I make a new duplicated PR but from my fork?

No, it's perfectly fine, just a tip for next time.

…

-- Sincerely, Luís Ferreira @ lsferreira.net