Protobuf.Internal.Common

newtype Bytes

Representation of a bytes Scalar Value Type field.

On a message which has been decoded, The wrapped DataBuff will usually be a DataView. In that case, the DataView is a view into the received message I/O buffer.

For messages which you intend to encode, You may set the DataBuff to DataView or ArrayBuffer, whichever seems best.

The ArrayBuffer and DataView are mutable, so be careful not to mutate them if anything might read them again. Here we trade off typechecker guarantees for implementation simplicity.

Constructors

• Bytes DataBuff

Instances

• Show Bytes
• Eq Bytes
• Newtype Bytes _
• Default Bytes

  Zero-length

type FieldNumber = UInt

data WireType

https://developers.google.com/protocol-buffers/docs/encoding#structure

Constructors

• VarInt
• Bits64
• LenDel
• Bits32

Instances

• Eq WireType
• Generic WireType _
• Ord WireType
• Bounded WireType
• Enum WireType
• BoundedEnum WireType
• Show WireType

class Default a  where

In Protobuf, zero values are “default values” and have special semantics.

Members

• default :: a
• isDefault :: a -> Boolean

Instances

• Default String

  ""

• Default Int

  0

• Default UInt

  0

• Default Int64

  0

• Default UInt64

  0

• Default Float32

  0.0

• Default Number

  0.0

• Default Boolean

  false

• Default Bytes

  Zero-length

fromDefault :: forall a. Default a => Eq a => a -> Maybe a

Turns a “default” (zero) value into Nothing.

label :: forall m s a. Monad m => String -> ParserT s m a -> ParserT s m a

If parsing fails inside this labelled context, then prepend the String to the error String in the ParseError. Use this to establish context for parsing failure error messages.

toDefault :: forall a. Default a => Maybe a -> a

Turns Nothing into a “default” (zero) value.

The Protobuf spec requires that a no presence field set to its “default” (zero) value must not be serialized to the wire.

When receiving messages we can use this function to interpret a missing no presence field as a “default” value.