Closed WhiffleFish closed 1 year ago
Yeah, this is super annoying. I do not know how to track it down though, ha. I guess we need to register POMDPs.jl 1.0 and remove POMDPs.@POMDP_require fully.
Is there anything stopping us from releasing a POMDPs.jl v0.10?
Anyways, it appears that changing @POMDP_require
calls to explicit POMDPLinter.@POMDP_require
calls fixes the issue.
If we're willing to admit this temporary workaround I can open a PR. If not, semver would suggest that moving from 0.9 to 0.10 would admit breaking changes. So technically it would be fine to remove POMDPs.@POMDP_require
along with POMDPs.@req
, POMDPs.@subreq
, etc. in that version bump, no?
fixed by #466