PDDL’s explicitly stated requirements were, arguably, a bad idea, and many competition domains don’t declare them correctly.
Aside from computing requirements implicitly from the set of actually used features (see #7), all errors related to incorrectly declared requirements should be turned into warnings, with the recommendation to leave the requirements section away entirely.
PDDL’s explicitly stated requirements were, arguably, a bad idea, and many competition domains don’t declare them correctly.
Aside from computing requirements implicitly from the set of actually used features (see #7), all errors related to incorrectly declared requirements should be turned into warnings, with the recommendation to leave the requirements section away entirely.
patrick
added this to the plasp 3.1.1 milestone 2017-11-17 15:47:39 +01:00
patrick
self-assigned this 2017-11-17 15:47:39 +01:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
PDDL’s explicitly stated requirements were, arguably, a bad idea, and many competition domains don’t declare them correctly.
Aside from computing requirements implicitly from the set of actually used features (see #7), all errors related to incorrectly declared requirements should be turned into warnings, with the recommendation to leave the requirements section away entirely.