Is there a Tricky Names for Nubies page?
We might save some stack-overflow searches.
In the spirit of Honest Trailers: if we named functions for what they do:
or-> first-truthy
some -> first-satisfying
some? -> not-nil?
any? -> return-true
Are there others?
--
You received this message be
Any case where valid? returns false and explain-data returns nil is a bug.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient
Nice work Oliy. I especially liked the re-frame section as I work at Day8
on re-frame. I liked what you did with the HTTP handler, much cleaner :)
On Fri, Nov 11, 2016 at 1:15 AM Oliver Hine wrote:
> Hi Erik,
>
> One of the philosophies of Martian was that it was not a "closed" system
> so that
I've just deployed a new release of functional-vaadin, a Clojure library
that greatly improves the building of Vaadin-based web UI's. Latest version
is 0.2.1, and adds
- New builders for tree tables, upload and login form
- Internal refactoring, including the use of clojure.spec for builde
s/explain doesn't produce any sort of error/output that I can see.
s/explain-data returns nil.
s/explain-str returns the last few lines printed by the function being
exercised. Maybe it captures output from the final test run?
On Sun, Nov 13, 2016 at 10:22 AM, Josh Tilles wrote:
> Just going o
Just going on memory at the moment, but I’m pretty sure `s/explain` just
writes to `*out*` (and thus always returns `nil`). You probably want
`s/explain-data` or `s/explain-str`.
-Josh
On Sun, Nov 13, 2016 at 10:58 AM James Gatannah
wrote:
> One of my system boundary data structures is particul
Turns out I was wrong about the minimal use case.
This particular problem was just an fdef that was missing a :ret spec.
That seems like a bug in s/explain, but I think it's a tossup whether
the bug's in the docstring or the implementation.
And I'm not entirely convinced that it's a bug at all.
One of my system boundary data structures is particularly ugly. It
involves things like JNI classes wrapping native socket libraries, go
loops, and higher-order functions that I can use to plug in message
dispatchers.
I'm in the process of translating it from schema to spec. So far, the
proce
