1. 19 Nov, 2018 1 commit
  2. 08 Nov, 2018 10 commits
  3. 31 Jan, 2018 1 commit
  4. 15 Aug, 2017 1 commit
  5. 14 Aug, 2017 2 commits
  6. 05 May, 2017 1 commit
  7. 10 Apr, 2017 2 commits
  8. 12 Feb, 2017 2 commits
  9. 22 Nov, 2016 1 commit
    • Steve Losh's avatar
      housekeeping · 85f82ed8
      Steve Losh authored
      fix typos in docstring and error messages.
      85f82ed8
  10. 27 Oct, 2016 5 commits
  11. 23 Aug, 2016 1 commit
    • Attila Lendvai's avatar
      numbers.lisp/lerp: The correct version is numerically stable, · 926a0666
      Attila Lendvai authored
      at the expense of an extra multiply. The unstable version can often be
      converted to a fast instruction on a lot of machines, though this is
      machine/implementation specific. As alexandria is more about correct code,
      than efficiency, and we're only talking about a single extra multiply,
      many would prefer the stable version.
      
      Patch by github.com/mfiano.
      926a0666
  12. 03 Apr, 2016 3 commits
    • Jan Moringen's avatar
      use implementation's EMPTYP when available · afaf1a16
      Jan Moringen authored
      Using the implementation's EMPTYP has the potential advantage of
      supporting user-defined sequence types (as is the case with SBCL).
      
      This commit tests for SEQUENCE:EMPTYP and defines ALEXANDRIA:EMPTYP in
      terms of it.
      
      For implementations that do not provide SEQUENCE:EMPTYP, nothing
      changes.
      afaf1a16
    • Jan Moringen's avatar
      use EMPTYP instead of e.g. PLUSP and LENGTH were appropriate · 8b89a71b
      Jan Moringen authored
      EMPTYP usually (except, maybe, for some user-defined sequence types) has
      two advantages:
      
      1. it has O(1) runtime while LENGTH can be O(n)
      
      2. it can work on user-defined, infinite sequences (given implementation
         support and integration of ALEXANDRIA:EMPTYP with the
         implementation's mechanism as is the case for SBCL)
      8b89a71b
    • Jan Moringen's avatar
      add READ-STREAM-CONTENT-INTO-{STRING,BYTE-VECTOR} · dce97236
      Jan Moringen authored
        export and document them
      
        use them in READ-FILE-INTO-{STRING,BYTE-VECTOR}
      
        no smoke test for READ-STREAM-CONTENT-INTO-BYTE-VECTOR due to lack of
        something like WITH-INPUT-FROM-BYTE-VECTOR
      dce97236
  13. 02 Apr, 2016 2 commits
  14. 27 Apr, 2015 1 commit
  15. 30 Jul, 2014 3 commits
  16. 12 May, 2014 1 commit
  17. 04 Mar, 2014 3 commits