No movement in 10 years -- I'm closing this as part of a little spring clean-up we're doing. If someone would like to work on something like this, feel free to reopen.

More generally, we're moving towards having fewer "it would be nice if someone implemented this" wish or feature request issues and focus more on things with immediate plans to implement. This does not apply to bug reports, which are always welcome.

I agree - this can wait

I'm sure we discussed something along those lines in the tracker already, but I
can't find it any more.

Brief comment: I think this would be useful, but with 90 open issues, I'd focus
on fixing the current code first. Or, phrased more strongly: we're in bugfix-
and cleanup-only mode, with other changes only permitted if there's a really
good reason.

What is clear is that when facing something that is *not* supported, the planner
should exit rather than producing garbage or segfaults.

Regarding checking about axioms/conditional effects/non-unit cost actions/zero 
cost actions/...
I suggest we implement some sort of capabilities system 
(similar to weka), which would give us a convenient way of checking all of 
these. 

The interface would be something like two boolean method for each "problematic" 
feature (axioms/conditional effects/...) - one saying whether it's supported, 
and the other whether it's supported and still admissible.

This interface should be implemented by heuristics, search engines, landmark 
graphs, and probably a few more things I haven't thought of.

Comments?