We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
There are places in ltest that have to do some very ugly destructuring:
ltest/src/ltest.lfe
Line 146 in ff9d44e
This is due to Erlang having some pretty ugly (also probably quite old) error-creation for assertions, e.g.:
Let's create some records (just the ones that are necessary) to at least keep our code clean.
These are going to need LOTS OF TESTS.
The text was updated successfully, but these errors were encountered:
This will show other similar ugly spots: git grep ',_ ,_' (all in the listener code).
git grep ',_ ,_'
Two of these are errors.
One is an ok.
Four are descriptions of ebins / modules.
One is test data.
These could all use some records ...
Sorry, something went wrong.
I'm not 100% convinced about the usefulness of this, really ...
In theory, sounds great, but in practice, I'm not sure it would be used much. Maybe in one or two places with little impact?
No branches or pull requests
There are places in ltest that have to do some very ugly destructuring:
ltest/src/ltest.lfe
Line 146 in ff9d44e
This is due to Erlang having some pretty ugly (also probably quite old) error-creation for assertions, e.g.:
Let's create some records (just the ones that are necessary) to at least keep our code clean.
These are going to need LOTS OF TESTS.
The text was updated successfully, but these errors were encountered: