`an` language chain affects `length` language chain?
See original GitHub issueChai 3.4.1, Node 4.2.2:
expect([1, 2, 3]).to.be.an.instanceOf(Array).and.to.have.length.below(1000)
… should work, but fails because length
returns 0
.
Removing an
from the chain, leaving:
expect([1, 2, 3]).to.be.instanceOf(Array).and.to.have.length.below(1000)
works as expected.
Seems similar to an issue reported late in #427 by valscion.
Issue Analytics
- State:
- Created 8 years ago
- Comments:12 (7 by maintainers)
Top Results From Across the Web
Acquisition of Clause Chaining in Six Languages - Frontiers
Diverse study designs for the different languages could have affected clause chain length, by both delimiting discourse genre and shaping ...
Read more >Acquisition of Clause Chaining in Six Languages - PMC - NCBI
Diverse study designs for the different languages could have affected clause chain length, by both delimiting discourse genre and shaping ...
Read more >The Information Chain Theory - SIUE
Language carries the largest amounts of information the shortest chain distances. Written words carry smaller amounts of information longer chain distances.
Read more >Language Models Perform Reasoning via Chain of Thought
In recent years, scaling up the size of language models has been shown to be a reliable way to improve performance on a...
Read more >Kids who learn 'clause-chain' languages are quicker to ...
These long sentences are known as “clause chains”. Unlike in English, where most of the clauses in a story would make sense if...
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 FreeTop 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
Top GitHub Comments
I think this has been as solved as we can for now, so we’ll close it 😄
Note: This has been partially solved at #642. Please read that PR for more details.
@keithamus should we close this or not, as it has been partially solved?