By using the latest Faker library, I’ve typed
which just stuck the iex, along with a high cpu usage in backgroud.
IMO its such a obvious bug, so why the exception is not handled? Is it designed on purpose or just a bug?
I am gonna wager that locking up the process in an infinite loop is not a desired outcome.
I agree with @benwilson512 though that is perfect example of garbage in, garbage out principle.
It ends up trying to find the last element of a
Stream.repeatedly, which is going to take a while…
You mean that I may should start an issue?
Even better, send PR instead.