nand

[char0n]

export const nand = complement(and);

[char0n]

@Undistraction

and in ramda is defined with Hindley-Milner signature a → b → a | b
This means that and can process any types, not just Booleans and can return any types.

Example of what I mean

R.and(1, 2); // => 2
R.and("test", "test1"); // => "test1"

Keeping this in mind, if we implement nand as complement of and it will always return Boolean.
The signature be then a → b → Boolean

Are we okay with that ? Does any usecase for this exist ?

@BjornMelgaard any opinion on this ?

[srghma]

@char0n
What we should return otherwise? first parameter? there is or for this
I think its fine to return boolean and be closer to ramda as possible

[char0n]

@BjornMelgaard the question was rather, do we need something like this in the lib ? ... rather then what it should return. It can return Boolean, and Boolean only,

[srghma]

@char0n if someone wants to, I've never used complement of and, I would rather add complement of path and prop

[Undistraction]

Complement of Ramda's and.

• T T = F
• T F = T
• F T = T
• F F = T

See: #234

[dawehner]

This is implemented in #952