sjrd on 0.6.x
Remove dead code: specific coll… Adapt the signature of `js.Arra… Merge pull request #3554 from s… (compare)
sjrd on master
Fix analyzer cycle detection to… Add toString methods to analyze… Do not provide linked ClassInfo… and 1 more (compare)
sjrd on master
Remove Logger.success It is un… Make level helpers final Clean-up ScalaConsoleLogger cod… and 1 more (compare)
Build.scala, it might need an explicit import of the
Hi there :wave: I have a couple of open pull requests for different repositories around Scala.js. Ideally, I would love to get feedbacks & be able to participate in the community. (feel free to discard this comment if it is not in the correct conversation)
Anyway, thank you to all the people involved in this project and for the time spent!
js.Dynamic.literal()to produce a crude codec, which is boring but ok, but I'm wondering about the allocate costs of such a thing (?) and thought I'd see if there was a simpler/better solution? I would be doing this 60 times per second...
we don't use web workers, but for lots of small objects we do use literals, but our data structures are small and not recursive, so hand cranking those codecs is simple.
In a different usecase with a huge recursive case class I'm using upickle, but the size of the result doesn't please me - so I want to give boopickle a go, which should improve the serialisation roundtrip. I wonder if it can benefit from 1.4.0 typed array improvements?
Array[Byte]will be represented by a typed-array, like
Int8Array? Then, if I have an
ArrayBuffer, is there a straight forward way to get an
Array[Byte]without copying? Like is there a better way than doing
new Int8Array(ab).toArray[Byte](is that even correct?)?
ByteBuffer(without copying): http://www.scala-js.org/api/scalajs-library/latest/scala/scalajs/js/typedarray/TypedArrayBuffer$.html