Evalable sometimes decides to gist things when it shouldn't
Nobody has claimed this yet.
- Dominant language
- Raku
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
<AlexDaniel> m:
for ‘foo bar baz’.match: :g, / (\w+) / { say $/ }
<evalable6> AlexDaniel, rakudo-moar 1761f953d: OUTPUT: «(｢foo｣ 0 => ｢foo｣ ｢bar｣ 0 => ｢bar｣ ｢baz｣ 0 => ｢baz｣)(｢foo｣…»
<evalable6> AlexDaniel, (｢foo｣ 0 => ｢foo｣ ｢bar｣ 0 => ｢bar｣ ｢baz｣ 0 => ｢baz｣)(｢foo｣ 0 => ｢foo｣ ｢bar｣ 0 => ｢bar｣ ｢baz｣ 0 => ｢baz｣)(｢foo｣ 0 => ｢foo｣ ｢bar｣ 0 => ｢bar｣ ｢baz｣ 0 => ｢baz｣)
So it was expecting that the message will be automatically gisted (because it is too long), but it turned out that it is not long enough.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating Evalable's logic for deciding when output should be turned into a gist, then reproduce the quoted match command and compare the output length with the threshold. Done means output of this size is handled according to the expected automatic-gisting behavior, with a regression check for the example.
Written by the indexing model from the issue text.
Assessment
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100