Skip to content
Snippets Groups Projects
  1. May 29, 2019
  2. May 28, 2019
  3. May 25, 2019
  4. May 20, 2019
  5. Dec 03, 2018
  6. Dec 02, 2018
  7. Nov 19, 2018
  8. Nov 08, 2018
  9. Jan 31, 2018
  10. Aug 15, 2017
  11. Aug 14, 2017
  12. May 05, 2017
  13. Apr 10, 2017
  14. Feb 12, 2017
  15. Nov 22, 2016
  16. Oct 27, 2016
  17. Aug 23, 2016
    • 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
  18. Apr 03, 2016
    • 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
Loading