mark lister
mark lister
@bblfish How does this look? ``` scala scala> import scala.collection.mutable.ArrayBuffer import scala.collection.mutable.ArrayBuffer scala> val a= ArrayBuffer[Byte]() ++ "abc".getBytes a: scala.collection.mutable.ArrayBuffer[Byte] = ArrayBuffer(97, 98, 99) scala> a.toBase64 res0: String = YWJj...
The latest commit (and I published it to bintray) supports a `Seq[Byte]` `ArrayBuffer [Byte]` etc. java.nio.ByteBuffer has an `array()` method. @bblfish, if I read your initial post correctly you're deriving...
So would ``` sig.asInstanceOf[ArrayBuffer].toBase64 ``` not work?
Ah! I see! I had it confused with http://www.scala-lang.org/api/current/index.html#scala.collection.mutable.ArrayBuffer
Yeah, I bumped into this same problem a few years ago. See my basen lib.
Because I originally used opencsv then switched to an internal parser the parser conforms to opencsv's api. There is no reason not to do this. I'll look into it.
``` scala> val csv = """1,2,3 | 4,5,6""" csv: String = 1,2,3 4,5,6 scala> new CSVReader(csv).toList res7: List[Array[String]] = List(Array(1, 2, 3), Array(4, 5, 6)) ``` This is a documentation...
``` scala> new CSVReader(new java.io.StringReader(csv)).toList res13: List[Array[String]] = List(Array(1, 2, 3), Array(4, 5, 6)) ``` There must be some implicit going on in the first example. Use the second.
Yeah, the core of the project is `CollSeq`, so overemphasizing our csv capabilities is probably not a good idea...
Not bad. I'll mull on it for a while see if it stands the test of time...