Closed gilch closed 1 year ago
Hmm, that's weird. It's like the progn
macro isn't in scope of the Sybil doctest. Didn't the other macros work?
Ah, I see it. I've put hidden doctests to copy in the _macro_
ns at the top of the files that need it. I wasn't able to do that here until I had the comment string macro defined, which happens just about as soon as possible, but after the bootstrap macros, one of which happens to be progn
. Options:
<<#
.<<#
up as far as possible, into the bootstrap section, and then move the hidden doctest immediately after that.progn
after the definition of <<#
and attach it to the progn
function object. Probably the easiest fix. I've already done this for the docstring of <<#
itself (because how else could that work?)Merging #189 (d691959) into master (a97e14c) will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## master #189 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 6 6
Lines 700 700
Branches 111 111
=========================================
Hits 700 700
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more
Well, that was easy. The hidden doctest didn't contain a "
character, so I could use a normal string literal. Come to think of it, even if it had, I was discarding that comment string anyway with _#
, because Sybil just reads the text statically. I didn't need the <<#
to build it into a string at all. Just including the extras would have been sufficient for Sybil. I just needed some way to discard them.
Just moving stuff over.