HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
whatyouhide
stream_data
Elixir2017–2017
whatyouhide / stream_data

stream_data

Data generation and property-based testing for Elixir. 🔮

2Distinct people
3Mentions
0Explicit recommenders
953GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Data generation and property-based testing for Elixir. 🔮

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 10:02:42 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week3 dated mentions

Observed mentions: 2017-08-17 19:13:41 UTC to 2017-10-25 19:07:28 UTC. Weeks start Monday, UTC.

0122017-08-14 00:00:00 UTC to 2017-08-21 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 142017-08-21 00:00:00 UTC to 2017-08-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-28 00:00:00 UTC to 2017-09-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-09-04 00:00:00 UTC to 2017-09-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-09-11 00:00:00 UTC to 2017-09-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-09-18 00:00:00 UTC to 2017-09-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsSep 182017-09-25 00:00:00 UTC to 2017-10-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-10-02 00:00:00 UTC to 2017-10-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-10-09 00:00:00 UTC to 2017-10-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-10-16 00:00:00 UTC to 2017-10-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-10-23 00:00:00 UTC to 2017-10-30 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsOct 23

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Aug 142017-08-14 00:00:00 UTC2017-08-21 00:00:00 UTC101
Aug 212017-08-21 00:00:00 UTC2017-08-28 00:00:00 UTC000
Aug 282017-08-28 00:00:00 UTC2017-09-04 00:00:00 UTC000
Sep 42017-09-04 00:00:00 UTC2017-09-11 00:00:00 UTC000
Sep 112017-09-11 00:00:00 UTC2017-09-18 00:00:00 UTC000
Sep 182017-09-18 00:00:00 UTC2017-09-25 00:00:00 UTC000
Sep 252017-09-25 00:00:00 UTC2017-10-02 00:00:00 UTC000
Oct 22017-10-02 00:00:00 UTC2017-10-09 00:00:00 UTC000
Oct 92017-10-09 00:00:00 UTC2017-10-16 00:00:00 UTC000
Oct 162017-10-16 00:00:00 UTC2017-10-23 00:00:00 UTC000
Oct 232017-10-23 00:00:00 UTC2017-10-30 00:00:00 UTC211

What Hacker News says

1 sources
Yes. Superficially, `do ... end` blocks look like English, because they are English words. On the other hand, they don't really correspond to any real grammar construct of the English language. They live in the the uncanny valley where you try to read it like English, but you can't actually read it as such. For some reason, the use of keywords like `def`, `defmodule` or `defmacro` doesn't bother me as much. Maybe because they are not block delimiters? In my opinion, braces, delimiters or parenthesis create less visual noise than endless cascades of `end` keywords: def f(x) do ... end end end end There are other block keywords besides `end`, which serve no purpose other than simplify some keyword list arguments at the cost of higher complexity. In general there is too much syntax sugar for thi
Read the rest
ngs that don't really benefit from it. Parenthesis in function calls are optional in some places but not others, which creates some unnecessary confusion. The syntax for anonymous functions is fn arg -> do ... end The `end` keyword is strange and I keep forgetting it (that's more a problem with me than the syntax, I know). The language is subtly whitespace sensitive in some places, while being mostly whitespace insensitive. Macros can't take a variable number of arguments, which leads to the proliferation of Special Forms (it's a kind of macros that is treated as special by the compiler) which could perfectly be macros if it weren't for this limitation. For a situation where this causes problems and requires some extra weirdness in what should be a simple DSL, look at this Github issue in the new testing library scheduled for inclusion in the standard library: https://github.com/whatyouhide/stream_data/issues/21
In Elixir in Depth – Reading and personal notes

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.