rfw

Seems like an extremely reductive view to take: you can't use time and family to buy food.

Gender roles aren't so cut and dry any more. Given that, maybe outcomes should be considered independent of gender?

Characterizing people wanting to contribute to the basic living conditions of people so pejoratively as 'unfortunate' and a 'continuation of the "white man's burden" ideology' is an extremely bad faith view of those who choose to do so.

We can implement it with a single `amb` function, too (I took some shortcuts that might have hidden some of the nature of the implementation)!

    -- Lifts a list into Amb.
    amb :: [a] -> Amb a

    amb = id

    amb [1, 2, 3] >>= \x ->
    amb [4, 5, 6] >>= \y ->
    if x * y /= 8 then amb [] else pure () >>
    pure (x, y)

    amb [1, 2, 3] >>= \x ->
    amb [4, 5, 6] >>= \y ->
    when (x * y /= 8) (amb []) >>
    pure (x, y)

It ends up looking like continuation-passing style: conceptually, if we encounter `amb []` in the nested function, the nested computation ends and we start examining the next value in the list values being assigned to `x`: the implementation given in the original post does end up using callcc, so with some imagination you might be able to derive some kind of equivalence here :)

amb without side-effects can also be expressed in terms of the List monad, e.g.:

    do x <- [1, 2, 3]
       y <- [4, 5, 6]
       if x * y == 8 then pure (x, y)
                     else []

    [(x, y) | x <- [1, 2, 3], y <- [4, 5, 6], x * y == 8]

1. https://en.oxforddictionaries.com/definition/inclusivity

The practice or policy of including people who might otherwise be excluded or marginalized, such as those who have physical or mental disabilities and members of minority groups.

2. Without an understanding of power, is there a useful definition of "inclusivity"?

Or is it just a whitewashed feelgood platitude that can't mean anything in the end, because if you include everyone, including people who are decidedly discriminating against you, that it constitutes some ideal of "inclusiveness"?

Dismissing a position as "virtue signaling" is fundamentally lazy.

Ironically, aren't you "virtue signaling" right now about how you're sincere enough to be able to look down on people who do it?

Inclusivity is about wanting to better include minorities or disabled people in spaces where they may have been discriminated against and affecting their livelihoods, e.g. the workplace.

Using a definition of inclusivity here without a consideration for power dynamics between the parties involved is totally uncharitable: as you've observed in your comment, there is no barrier to actually denying "exclusive rights" to activists, so it's more a matter of respect to the people who want to use the symbol (e.g. the pride flag, which few people have issues with it being used to exclusively represent LGBT groups) to make their cause more visible, rather than a lack of "inclusivity".

On what grounds should an unrelated party (the government, via labor law) force their will on two voluntarily trading parties, blocking their transaction?

Because wage slavery exists and you can't shrug your shoulders and say "well, they're choosing to work for peanuts so it's fine!".

It really doesn't depend on the jail, at all. Having to be incarcerated to have a good livelihood is unforgivably disgusting.

If you can spend enough money to say "well, that's not my problem", then you yourself are the problem.

If you watch the GIF, the library parses Japanese addresses just fine.

What does diversity of thought even mean?

Nat = Nat + 1 does end up being meaningful: since ultimately the numbers that fall out (e.g. Bool = 2) end up describing the sizes of sets, an interpretation of Nat is some infinite cardinal (aleph-null), which is the size of the set of natural numbers.

Quantum computing is not parallel computing: https://physics.stackexchange.com/a/3400 briefly talks about the mechanism of quantum computing and how it is not general parallelism.

Can you refute the claims in the video posted? The style is unrelated to the validity of the claims.

The SNAP Inc. in question is actually http://www.snapinc.net, an enterprise consultancy.

You want people to mine for you for... nothing in return?

It's just a convention.

Forgive me if I misunderstand, I still don't understand your concern – TypeScript has type safety because it can check types at compile time (vs. JavaScript which has very limited type safety at run time). I don't think it's fair to call it a facade, because it is definitely commonly accepted as type safe.

The US announced their participation in the TPP in 2009, a free trade agreement encompassing trade between the US and New Zealand. The Obama administration had been very gung-ho about its ratification in the US, so I don't think the question of nuclear powered warships comes up much anymore.

I don't think you can squarely point to the New Zealand–China FTA for whichever interpretation of colonization you'd like – immigration laws were mostly unchanged by the FTA with the exception of short term work visas, and property purchases by Chinese investors is not an exclusively "countries who have negotiated free trade agreements with China" phenomenon (see Vancouver in Canada, Seattle in the US).

Then you get H-1B fraud complaint fraud ;)

I think most people wouldn't know the difference (I had no idea!) and the knowledge might fall into the realm of obscure trivia.

The parent comment makes no reference to right wing news, or even any judgment on the fakeness of left or right wing news.

Neat! Extension methods and getting rid of "var that = this;" in one!

It seems that it also extends to full expressions on the right-hand side of ::, so you can even do, for using Array operations over things that look like arrays but not quite:

    document.querySelectorAll('p')::([].map)(f)

    [].map.call(document.querySelectorAll('p'), f)

The rule is misleading in cases like:

    int* arr[][10];

Instead, when you write declarations, do it from right-to-left, e.g.:

   char const* argv[];

It doesn't help with reading, unfortunately.

It probably goes without saying that such egregious corner-cutting shouldn't be happening regardless of being rich or poor.

Really? Color me corrected, then :) Does the compiler need a SAT solver then to make sure all the constraints hold?

Unfortunately, the usefulness is limited – the size of all Vects must be known at compile time. While this does prevent a large class of bugs that arise from incorrect compile-time knowledge, the size of the class of runtime bugs affected by this is a lot smaller, as for each differently-lengthed Vect, a distinct instantiation of the Vect type needs to exist at compile-time.

I believe Compcert still translates programs with undefined behavior and doesn't really do anything about it; or rather, the behavior is defined but based on whatever the Compcert authors define the behavior to be.

I love the idea! A few examples are a bit strawmanish but really when you're comparing languages like that who can resist the strawman.

The Clojure solutions do sacrifice a lot of safety though, due to dynamic typing (e.g. the visitor pattern, which relies on basically strings to do its dispatching).