This seems really interesting, and useful – thanks!
I was curious about any (redacted) details of the kinds of "large systems"
for which this would be useful, but the docs in the PR are pretty clear –
this is a "dead-simple way to parallelize" dynamic supervisors by running a
group of such
That is pretty much what I was using (it is what we use in Elixir core
when an exception is raised),
the issue with that is the it does not play out well with multi-line
return values, which was my use case, and therefore this proposal.
On Fri, 10 Dec 2021 14:42:51 +0100
Wojtek Mach wrote:
>
Another popular pattern I've seen in the wild is:
## Examples Foo.bar() #=> :baz
since :baz is in a comment, it is not going to be syntax highlighted,
but I think that's fine.
On December 9, 2021, elixir-lang-core wrote:
> Hi list,
> documenting functions made me realize the need to be able to
That's a nice trick Eric.
I didn't now about it, it formats well in ExDoc, with the exception that
">" is not hightlighted and it is selectable., but I can create a
feature request for MakeUp.
So far the only way I knew to disable it is not to use `iex>`
altogether.
Thank you
On Fri, 10 Dec
I don't think this is needed since if you don't want to use doctests you
don't have to use the doctest syntax.
For example, instead of:
iex> 1 + 1
2
you can do:
> 1 + 1
2
On Thursday, December 9, 2021 at 3:44:55 PM UTC+1 eksperimental wrote:
> Hi list,
> documenting functions made me
Processes like Task.Supervisor and DynamicSupervisor can become bottlenecks
on large systems and at the moment there is no dead-simple way to
parallelize those. A minimal solution takes about 30-50 LOC and I believe
it is important for the language to have an out-of-the-box solution to
tackle
