Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
atom_concat/3 throws type_error/2 when you pass in two different primitives
See original GitHub issueIn swipl, this works
?- atom_concat('hello',42,Foo).
Foo = hello42.
in Tau, it’s giving me type_error/2. Just wanted to let you know in case this was not a known issue.
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
SWI-Prolog-7.2.2.pdf - Fedora Package Sources
Stops scanning for more arguments, so you can pass arguments for your application after this one. See current prolog flag/2 using the flag ......
Read more >Reference Manual - SWI-Prolog
Stops scanning for more arguments, so you can pass arguments for your ... In summary, there are really two distinct ”tracing” features: trace...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Unlike in SWI-Prolog, the implementation of the
atom_concat/3predicate in Tau Prolog is ISO Prolog Core standard compliant. Thus, a type error for that query is the correct and expected result. To concatenate two atomic terms, use instead theatomic_concat/3built-in predicate.Thanks for the help @pmoura! In fact, it’s time to update.