Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update with master #5

Merged
merged 98 commits into from
May 16, 2021
Merged

Update with master #5

merged 98 commits into from
May 16, 2021

Conversation

jfacorro
Copy link
Member

No description provided.

borkdude and others added 30 commits March 2, 2019 21:06
This matches the pom.xml at least.
curtis.io seems to be missing most of its content
Caused by implicitly using a private var.
The old version isn't compatible with newer jvms, I don't think.
Fixes TCHECK-14

Now it's mostly a basic menu of links.
The clojure dev sites got overhauled sometime in the last year.
They were confusing/misleadingly named. I kept `gen/nat` since it's
used quite a lot, and added `gen/small-integer` for when you want
negatives, but otherwise just described in the docstrings how to get
the same behavior.
The first bigint generator, it explicitly specifies that it's bounded
by a function of the `size` parameter; this is in contrast to earlier
approaches I tried where for any given `size` the distribution would
still be unbounded, but smeared differently.

Describing the distribution in the name leaves room for later adding
other bigint generators that behave differently.

I didn't add it to cljs, since it's unclear what to generate there,
and so ratio uses large-integer instead. It just ends up being doubles
on cljs anyhow so that part doesn't matter much.
This is a sad workaround for the eternal problem that collections
containing NaNs, when not `identical?`, cannot be `=`.

The name is more generic as there could conceivably be other objects
added to gen/any & friends that don't qualify for the equable
variants, e.g. (Object.)s.

The word "equatable" could arguably imply the wrong concept of "can be
passed to =", but since everything can be passed to = in clojure (just
like every object implements .equals on the jvm), I'm not worried
about this.
Github pages interprets the {{ as a special syntax, and I don't know
how to make it not do that, so this is easier. It's a bit remarkable
that that only shows up in one place.
1) Add a doc page for version-specific API docs
2) Enumerate exactly which doc pages should be
   included in the codox output
3) Config for linking to the github source
Should fix the jenkins build.
I had updated the test so that it no longer intentionally excluded
infinite doubles, which works fine on 1.9 and later; this change
excuses failures involving infinite values on versions of clojure that
don't have a syntax for infinity.
Wouldn't it be great if git had a mechanism for annotating old commit
messages or something of that sort?

Anyhow I noticed that commit 5e2734f has an incorrect commit
message due to too much `git commit --amend`ing, and I wanted to
at least say so in the git log.

(So this commit doesn't have any associated changes)

The wrong part is "rewrite ratio in terms of it" -- in reality,
gen/ratio was left alone and gen/big-ratio was added (jvm only),
documented as using `gen/size-bounded-bigint`.
@jfacorro jfacorro merged commit bbbf52e into clojerl May 16, 2021
@jfacorro jfacorro deleted the update-with-master branch May 16, 2021 01:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
5 participants