-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
most values are not captured #7
Comments
Thoughts, @igrep? |
I'm sorry for adding a big bug... I've scarcely used hood since the fix... Thank you very much! |
FWIW, I didn't suggest "moving incrementUniq node before the fn call" as a proper fix, as I think it basically undoes the fix from #6: we would no longer "[increment] the node id only when the function is executed without exception". If one wanted to do that, he could revert the whole commit. |
I too am a novice and ra ninto the same bug -- the simple examples print data as _. Very disappointing. As a beginner, I can't assess hood as a development tool, but it's intriguing and seems useful for learning haskell. |
The issue is still present in 2021. |
I'm new to Haskell and I don't know if or where I messed up, but none of the examples from the homepage work for me. Even something as simple as:
For functions the output value is displayed, but the input parameters are displayed as
_
:I'm using hood-0.3.1 and:
hood-0.3 works fine.
I tried using the GHCi debugger and it seems that the captured events (using 0.3.1) in the first testcase were:
while in the version 0.3 that works, the event with
Cons
has the ID = 3. Given thateventsToCDS
appears to use this ID as an index into theout_arr
array, this duplicate event ID seems to be the problem.Seems to be caused by the change to
unsafeWithUniq
in #6 -- movingincrementUniq node
before thefn
call fixes the problem for me.The text was updated successfully, but these errors were encountered: