Comments (4)
I like having a simple rule with a specific universal documented meaning so authors can use it to communicate properties of a function simply and precisely to their users. Unfortunately the current "convention" doesn't follow the rule quoted above; it's subjective, as seen in idiosyncrasies like rand(rng)
, print(::IOBuffer)
, and seed!(k)
, which makes it hard to use for precise communication between individuals.
Anyway that's just my personal rant, not your problem. Feel free to close this if you like.
from supposition.jl.
Unlike rand
(where the hidden state is always assumed to exist), the currently used test case does not always exist, so the bang serves as a reminder that there is some (hidden) state being modified when this is called. I'm feeling a bit uneasy about removing the bang there (and similarly with target!
and reject!
too) because of that.
It's a bit like Random.seed!()
, which seeds a (hidden) default.
from supposition.jl.
I'll do a small export-audit of everything that I consider API before registering, so I'll take a look at this then.
from supposition.jl.
Alright, I've reworked the exposed API. Everything now consistently uses <verb>!
from the user-side, to indicate the change of hidden state. I've also modified the internal uses to follow the usual convention.
from supposition.jl.
Related Issues (20)
- Allow more than one target score to be tracked
- Provide a way to set a global default configuration for `@check`
- Support giving a `minimum` & `maximum` to `Data.Floats`
- `Data.recursive` is mentioned but not documented HOT 1
- Have `@composed` assign its `Possibility` to the function name HOT 3
- Support `BigFloat`/`BigInt`? HOT 1
- Add a docstring for submodule `Supposition.Data`
- Align test summary column headers with columns
- Provide a way to configure the maximum allowed number of choices through `CheckConfig`
- Be smarter about `Overrun`
- Meta-Issue for the road to release
- [Doc]: Separate public interface from internals HOT 1
- TagBot trigger issue HOT 7
- [UX]: Better printing of `Possibility` subtypes HOT 1
- [Bug]: `SystemError` when running `@check` for the first time in a project without a stored database
- [UX]: Allow using anonymous functions & existing functions in `@composed`
- [Doc]: Unexplained jargon HOT 3
- [UX]: "Given expression is not a function call or definition" for short-form function definition
- [UX]: "An argument doesn't have a generator set!" HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from supposition.jl.