Skip to content

Introduce ?TYPE macro #296

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.

Sign up for GitHub

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

Open
michalmuskala wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Introduce ?TYPE macro #296

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
50fb72d
Introduce the ?TYPE macro
michalmuskala Jun 27, 2022
4814f7e
Update proper_typeserver.erl
kostis Jun 29, 2022
352a042
Update proper_typeserver.erl
kostis Jun 29, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 10 additions & 8 deletions src/proper_typeserver.erl
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -161,17 +161,19 @@
%%% </li>
%%% </ul>
%%%
%%% The `?TYPE` macro for explicitly taking advantage of PropEr's native type
%%% The `?TYPE' macro for explicitly taking advantage of PropEr's native type
%%% support is subject to the following usage rules:
%%% <ul>
%%% <li>It is allowed in any position to produce a PropEr type, including
%%% outside of `?FORALL`.</li>
%%% <li>The same restriction on allowed recursive native types as in `?FORALL` apply.</li>
%%% <li>There's no risk of confusion between expressions and native types,
%%% inside `?TYPE` everything is interpreted as a native type, and as such
%%% `?TYPE([integer()])` will produce an arbitrary integer list.</li>
%%% <li>It is not checked for correct syntax - using invalid syntax can produce
%%% errors when the property is evaluated, which are hard to understand.</li>
%%% outside of `?FORALL'.</li>
%%% <li>The same restriction on allowed recursive native types as in `?FORALL`
Comment thread
michalmuskala marked this conversation as resolved.
Outdated
%%% apply.</li>
%%% <li>There is no risk of confusion between expressions and native types.
%%% Inside `?TYPE' everything is interpreted as a native type; for example,
%%% `?TYPE([integer()])' will produce an arbitrary integer list.</li>
%%% <li>Its argument is not checked for correct syntax. Using invalid syntax
%%% can result in errors that are hard to understand when the property is
%%% evaluated.</li>
%%% </ul>
%%%
%%% You can use <a href="#index">these</a> functions to try out the type
Expand Down