You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Silly uses UDAs to name unittests. These UDAs are not normally available at runtime to the test runner, so Silly uses traits to fetch them from all known modules. It uses dub_test_root to do so, which has recently been deprecated.
I don't believe there exists a suitable replacement to access all modules at compile time, so I don't think it is appropriate to deprecate dub_test_root.
The text was updated successfully, but these errors were encountered:
If it's deprecated only to fix deprecation build failures, then maybe it would be a good idea to add some informative text inside the deprecation itself.
As it is the compiler's entry point, the module itself will not cause a deprecation warning, and it importing deprecating modules will not cause deprecation warnings (as there is no longer a transition of deprecation state).
So I suppose the only way to fix this would be to mark silly as deprecated from inside of itself?
Silly uses UDAs to name unittests. These UDAs are not normally available at runtime to the test runner, so Silly uses traits to fetch them from all known modules. It uses
dub_test_root
to do so, which has recently been deprecated.I don't believe there exists a suitable replacement to access all modules at compile time, so I don't think it is appropriate to deprecate
dub_test_root
.The text was updated successfully, but these errors were encountered: