Compilation warning about unsound assumption could lead to hard to understand errors
We have 4 (2 pairs of) warnings about unsound assumptions in Rudder when compiled with -Xlint (and we have tons of others about unused imports / tuple adapatation / etc, but let's start with the easy ones).
They don't seems to cause problem, but will eventually along some refactoring. One pairs is just a matter of declaring class in a higher scope than a class. The other seems to be an error in scala syntax understanding.
Updated by Vincent MEMBRÉ over 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.1.13 and 3.2.6 which were released today.
- 3.1: Announce Changelog
- 3.2: Announce Changelog
- Download: https://www.rudder-project.org/site/get-rudder/downloads/