Utkarsh Sharma
Utkarsh Sharma
So @LeonHibnik I solved this by downloading the latest backend it must be a different backend. I tried this earlier also but it never picked up the path from env...
Hey can I take this up?
I think adding a compiler warning of sorts is also one option. Somehting like: ``` Warning: assert without an error message Error: x Failed to generate execution trace `-> assertion...
Hey so was a bit busy last week and couldn't really work on this! I did the smt file but had a few doubts: Should the error message be in...
@katat I see the pr that you raised was closed for some reason. Is this something not desired anymore? or is it just too difficult to implement atm? imho it...
Got it so we can do this for hint functions atm. Can I take up this with #211 as they are kind of similar and make a single PR for...
@katat a question For only allowing if else in `hint` functions I would have to know when parsing the statement that whether it was in an hint function or not....
Also there is a thing with returning early from the ite statements. I think we have to also drill down the function's `return_type` into `parse_fn_body` so that we can pass...
> In parser phase, it would need to assume the ITE branches support statements. So we would parse ITE anyway and throw error at the type checker level > After...
> We already have the is_hint parsed and saved in FunctionDef. Can we just propagate this flag using the TypedFnEnv and use it to differentiate type check rules? Got it...