From: Tino Calancha <tino.calancha@gmail.com>
To: Alex <agrambot@gmail.com>
Cc: 27559@debbugs.gnu.org, tino.calancha@gmail.com
Subject: bug#27559: 26.0.50; [PATCH] Add tests for cl-macs.el
Date: Tue, 04 Jul 2017 14:04:14 +0900 [thread overview]
Message-ID: <87wp7oaj3l.fsf@calancha-pc> (raw)
In-Reply-To: <874luti81g.fsf@lylat> (Alex's message of "Mon, 03 Jul 2017 14:23:39 -0600")
Alex <agrambot@gmail.com> writes:
> That's more or less what I did at first, but I figured since cl-loop is
> a large macro, that it's best to quote the macro so that an accidental
> error doesn't halt testing.
I prefer just use (eval '...) in those cases where the expansion fails.
That way the file is more readable, and a reader focus her eye in those
failing expansions.
Maybe we could add a comment in the file saying that those
`should-error' are failing expansions to be fixed.
> For instance, some for-as-arith tests that aren't marked as should-error
> currently error in master. As an example, (cl-loop for i above 0 by 2
> downfrom 10 collect i) should work, but it errors. I have a working
> patch for these, but I wanted to make the tests first.
That's great! Looking forward to see the patch fixing these problems.
> It would be nice if the ert tests in general could just continue on with
> testing even if there are macro-expansion errors.
Sure, as long as the errors are expected.
next prev parent reply other threads:[~2017-07-04 5:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 5:54 bug#27559: 26.0.50; [PATCH] Add tests for cl-macs.el Alex
2017-07-03 9:42 ` Tino Calancha
2017-07-03 20:23 ` Alex
2017-07-04 5:04 ` Tino Calancha [this message]
2017-07-04 19:49 ` Alex
2017-07-05 13:29 ` Tino Calancha
2017-08-11 1:17 ` npostavs
2017-08-12 0:02 ` Alex
2017-08-22 0:55 ` npostavs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wp7oaj3l.fsf@calancha-pc \
--to=tino.calancha@gmail.com \
--cc=27559@debbugs.gnu.org \
--cc=agrambot@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.