1. '_' is actually a kind of match pattern and used a lot in the
specification, and '...' and be also considerd as an auxiliary seq match
pattern. I'm feeling strange that they're not re-exported in (srfi :262)
since other patterns (=>, quote, quasiquote, unquote, unquote-splicing)
are exported.

2. In spec, author proposed a procedure 'match-ellipsis?' and note that
the semantics of <<extended-ellipsis>> may be extended in future. In
that case, (srfi :262) should export its own 'ellipsis' binding to avoid
potential conflict with other libraries. And if such conflict happens,
it might change the semantic of a 'match' form that using ellipsis
silently.

(match (list 1 2 3)
  ;; If ... is not a match ellipsis, the following pattern will be
  ;; intrepreted as a list with two elements.
  ((list a ...)
    a))
--
Retrieve my PGP public key:
执行下列命令以获取我的 PGP 公有密钥：

  gpg --recv-keys B3EBC086AB0EBC0F45E0B4D433DB374BCEE4D9DC

Zihao / 閱卜錄