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.
wrong type printed for tuple containing null
See original GitHub issueIt seems that, at least on JS, the following is printing [ceylon.language::Null], whereas it should be printing [ceylon.language::null]:
import ceylon.language.meta {type}
print(type([null]));
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
What is the best way to check if a tuple has any empty/None ...
It's very easy: not all(t1). returns False only if all values in t1 are non-empty/nonzero and not None . all short-circuits, so it...
Read more >Incorrect inferred tuple names with null coalescing operator
I.e. they should both have '(string name, string)?' type. However, 'person2' has '(string name, string address)?' type. class Sample { void ...
Read more >Python: Check if Tuple is Empty - STechies
There are various ways to check for an empty tuple. using the not operator, using the len() function and comparing with another empty...
Read more >Python Tuples and Tuple Methods - Medium
A tuple with values can be initialized by making a sequence of values ... Lists and tuples are standard Python data types that...
Read more >Python Tuples - GeeksforGeeks
Tuple is a collection of Python objects much like a list. The sequence of values stored in a tuple can be of any...
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
Alright, I have now reviewed precisely what the spec says on this topic, and I’ve verified that the typechecker tests indeed test exactly the specified behavior. In fact, the typechecker is doing exactly what is defined in the spec, and @Zambonifofex’s original bug report is correct and that really is a minor bug in the JS metamodel stuff.
Note that the bug is very specific to
Nullvsnull, and doesn’t affectsmaller, for example.Fixed now, I believe.