steakhal wrote: @haoNoQ Do you recall why is a State bundled with a CallEvent? Sometimes that gets outdated as we manipulate the State. For example, within an eval::Call callback, by definition, we must always bind the return value, while the `Call.getReturnValue` will always return Unknown (because at Call construction time, that was not yet bound). Would it make sense to just not bundle a State alongside a CallEvent and be always explicit about the State? Alternatively, we could consider some strong typing technique to grant static guarantees about the validity of the attached State, but frankly that seems like an overkill.
https://github.com/llvm/llvm-project/pull/160707 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
