Skip to content
#

serialization

Here are 1,388 public repositories matching this topic...

jean-airoldie
jean-airoldie commented Jun 6, 2019

Here is some general documentation improvement suggestion regarding flatbuffers. This is what I remember struggling with (from the top of my head). Also some point might be a little bit opinionated.

Some of the points were taken from #5387.

  • Regarding the builder:
    • The fact that its kinda like an arena allocator used for serialization.
    • The concept of offsets, what do they repre
ensemblebd
ensemblebd commented Jun 3, 2018

Just saying. Including the legacy script or the everything script, and store is undefined.
RequireJS can't find it without explicitly specifying the context, unless you happen to throw the project in the root of your website which would be highly strange.

I've spent 30 minutes just trying to figure out how to use this damn thing. Incredibly frustrating.
Wish I could say it was a bree

zachelrath
zachelrath commented Jul 9, 2019

Currently, when SortMapKeys is set to true in Config, map keys are sorted using a standard alphanumeric sort. It should be possible to specify a custom map key sorting function to use, in order to prioritize certain map keys over others.

Example: Standard SortMapKeys behavior:

cfg := jsoniter.Config{
   SortMapKeys: true,
}.Froze()

m := map[string]int{
   "beta": 2,
   "alp
tetraptych
tetraptych commented Nov 11, 2017

DateType and DateTimeType and subclasses use datetime.datetime.strptime, which in turn uses the dateutil library. Unfortunately, this library is much slower at ISO8601 date parsing than C-based alternatives (in particular, ciso8601):

import datetime
import ciso8601
%timeit datetime.datetime.strptime('2018-01-01', '%Y-%m-%d')
# 10.5 µs ± 440 ns per loop (mean ± std. dev. of 7 r
breznak
breznak commented Oct 24, 2019

I see this project has hard-coded (copied) external source-files for dependencies.
I'd like to ask for documentation improvement on this topic:

  • which repo the come from, URL
  • what version/commit is being used?

And if possible, it would be great to see these updated (or replaced with actively developed forks/alternatives):

  • rapidjson:
    • does have a problem with releases l
qwwdfsad
qwwdfsad commented Jan 28, 2020

We should decide on KSerializer.equals (and hashCode) contract, document it and use internally as invariant everywhere.

Current sources of confusion:

  • Generic serializers and their equality
  • Object.serializer() != Object.serializer()
  • Sealed classes serializer
taleinat
taleinat commented Jul 3, 2019

TimestampSigner uses int(time.time()) to create timestamps, which will use the local timezone. However, it uses datetime.utcfromtimestamp to convert them into datetime objects, which will create naive datetime objects by interpreting the timestamp in the UTC timezone.

The fix should be to always write UTC timestamps. See [this StackOverflow question](https://stackoverflow.com/questions/

Improve this page

Add a description, image, and links to the serialization topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the serialization topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.