1. 03 Aug, 2018 1 commit
  2. 02 Aug, 2018 4 commits
  3. 31 Jul, 2018 1 commit
  4. 29 Jul, 2018 2 commits
  5. 27 Jul, 2018 3 commits
  6. 05 Jun, 2018 2 commits
  7. 02 Jun, 2018 2 commits
  8. 04 May, 2018 5 commits
  9. 03 May, 2018 1 commit
  10. 08 Apr, 2018 2 commits
  11. 07 Mar, 2018 5 commits
  12. 01 Mar, 2018 3 commits
  13. 20 Feb, 2018 3 commits
  14. 19 Feb, 2018 2 commits
  15. 17 Feb, 2018 2 commits
    • Eric Timmons's avatar
      Change apply to funcall in expansion of define-package · 21e3a85b
      Eric Timmons authored
      SBCL has been getting aggresive with checking arguments to functions. For some
      reason (as of SBCL 1.4.1), setting the package source location in define-package
      seems to trigger a source translation for the apply form that ends up producing
      (many) compilation notes that the arguments to ensure-package in the keyword
      positions are not constant, weakening keyword argument checking. We can get
      around that, however, by using a funcall directly.
      21e3a85b
    • Eric Timmons's avatar
      Evaluate sb-c:source-location after macroexpansion · ed0f4d5e
      Eric Timmons authored
      Tested on SBCL 1.4.4. If sb-c:source-location is evaluated during macro
      expansion, then the source location will always point to asdf.lisp (inside the
      define-package macro). If it is evaluated after macro expansion, it points to
      the right place.
      ed0f4d5e
  16. 16 Jan, 2018 2 commits