-
-
Notifications
You must be signed in to change notification settings - Fork 92
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
Main thread panicked (some errors) #310
Labels
Milestone
Comments
ah ok, yea no arg functions are compile time evaluated, could be some issue there. |
KtorZ
added
typechecking
Types and inference
code gen
Untyped Plutus Core code generation
labels
Jan 26, 2023
@alessandrokonrad is this still an issue? |
KtorZ
added a commit
that referenced
this issue
Feb 13, 2023
``` Error: × Main thread panicked. ├─▶ at crates/aiken-lang/src/uplc.rs:1451:52 ╰─▶ called `Option::unwrap()` on a `None` value ``` See also: #310
MicroProofs
pushed a commit
that referenced
this issue
Feb 15, 2023
``` Error: × Main thread panicked. ├─▶ at crates/aiken-lang/src/uplc.rs:1451:52 ╰─▶ called `Option::unwrap()` on a `None` value ``` See also: #310
MicroProofs
pushed a commit
that referenced
this issue
Feb 15, 2023
``` Error: × Main thread panicked. ├─▶ at crates/aiken-lang/src/uplc.rs:1451:52 ╰─▶ called `Option::unwrap()` on a `None` value ``` See also: #310
I think these are all passing or banned by type checker. Can you verify @alessandrokonrad? |
@MicroProofs it's all working great now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What Git revision are you using?
3c97f05
Command:
aiken check
Error:
Command:
aiken check
Error:
Command:
aiken check
Error:
Command:
aiken check
I was able to narrow this one down. It seems like it has to do with the no arg function
tx_1()
. If I add a random argument to it liketx_1(1)
then there is no error.The text was updated successfully, but these errors were encountered: