Explicit used in a sentence

Explicit in a sentence as an adjective

This allows you to explicitly state the assumptions about your inputs: how is this a bad thing?

"Mistake 3: Not being explicit about hacks" should be re-written, "Being Dishonest.

Any exposure to disease, customs, or technology without their explicit choice will **** them.

Turns out we don't, and we can do this explicitly with a rather complicated, yet beautiful, construction.

It is explicit, intentional putting-down of someone because they aren't as good at something as you are or think they should be.

Why should my computer have auditing capability, without my explicit knowledge or me making the decision to put it there?

But the difference is that Haskell lets you be explicit about whether you want side-effects or notits just another part of your interface.

Instead, its a different basis for programming which allows you to manage side-effects explicitly.

The other method of proving this though, the one where I asked you to explicitly engineer for me a B1-R1 pairing out of the larger pairing of all the six bags... that can still work.

You can refactor and move around most Haskell code without worrying about breaking its surroundings because any dependencies are explicit.

If I were interested in picking up an open-source project, I'd be hesitant to join one in which there had been explicit legal threats against the original author.

Technically, you can already, we just need to put together very explicit instructions and documentation that's different for each kind of proof.

This is why developers need explicit guidelines, because as they just demonstrated if there are no guidelines companies default to the thing that exploits the end user!

These people appreciate much more than other mathematicians a proof of some fact in an _explicit_ way, not requiring the Axiom of Choice, even if it's trivial when using the Axiom.

Its making side-effects first-class citizens: now you can write code that talks about having or not having them!You can still have side-effects however you want, you just have to be explicit about it.

See, the Axiom of Choice is not _explicit_: it says something like - under certain conditions - "a matching in pairs between these two sets exists, but I'm not showing you what it is explicitly, I'm just telling you it exists".

Every language has hundreds of tacit grammar rules, many of which are not known explicitly even to native speakers, but which reveal a language-learner as a foreigner when the rules are broken.

And this is how types like IO and ST help make your code easier to think about: any code that is not in a type like IO or ST can only depend on its arguments, making all the dependencies more explicit.

But a book teaching how to write code in the language is not a throwaway spike solution, and in that environment you should either explicitly tell readers you're teaching them a style that nobody else uses in production code or — and this is my preference — just write idiomatic code.

I am all for the interconnected web, and making it easier for me to introduce my friends to new content across it, however it has to be done on my terms, it has to require explicit authorisation and must never do something automatically without my consent.