Stefan Mandel

You use an `ExprsParser` but you did not extend `Exprs` by your alternative.

It seems to be a type hint. The argument of - `NumSymbol` is of type `&'input str` - `FactorOp` is of type `Opcode` Maybe this hint is not even needed,...

Problems occur with `webpack 4` together with `gulp/webpack-stream`. In this case the fileName is omitted completely leaving: ``` [3, 17]: Type boolean trivially inferred from a boolean literal, remove type...

I tried to fix this issue in a fork, yet this lets every unit test fail. So this would have meant a complete API change and I think it should...

Also check to keep the handling of this code consistent ``` @Test void testStacktrace2() { assertThat(0) .satisfies(x -> assertThat(x).isEqualTo(1)); } ``` Here the superfluous lines from the example above appear...

Maybe related:  The title bar appears with padding to the top. Clicking on the title bar elements has no effect, clicking the area above the title bar works. The...

Similar issue with `use std::fmt::{Display, Formatter, Result};`

The lines prefixed with `org.assertj.core.tests` should be visible. This is probably the case if the test is not in an assertj package, so no reason to worry about. Yet, I...

> I think we should remove all stack trace elements starting from the first assertj element. Look at your last example: ``` org.assertj.core.error.AssertJMultipleFailuresError: Multiple Failures (1 failure) -- failure 1...

Maybe it is just the fact that I read your statement to literal, In your stacktrace you find two (!) lines concerning the test : ``` at org.example.test.Remove_assertJ_stacktrace_elements_Test.lambda$should_$3(Remove_assertJ_stacktrace_elements_Test.java:67) ... at...