pkg debug/dwarf, const AttrDwoName = 118
pkg debug/dwarf, const AttrDwoName Attr
pkg debug/dwarf, const AttrElemental = 102
pkg debug/dwarf, const AttrElemental Attr
pkg debug/dwarf, const AttrEndianity = 101
pkg debug/dwarf, const AttrEndianity Attr
pkg debug/dwarf, const AttrEnumClass = 109
pkg debug/dwarf, const AttrEnumClass Attr
pkg debug/dwarf, const AttrExplicit = 99
pkg debug/dwarf, const AttrExplicit Attr

    that same scope. This is a breaking change from the behavior of RNNCells in
    TensorFlow versions <= 1.0.1. TensorFlow 1.1 had checks in place to ensure
    old code works correctly with the new semantics; this version allows more
    flexible uses of RNNCell but can lead to subtle errors if using code meant
    for TensorFlow <= 1.0.1. For example, writing: `MultiRNNCell([lstm] * 5)`

ok := coeffFromHalfByte(z0, p) if ok { a[j] = coeff j++ } if j >= len(a) { break } coeff, ok = coeffFromHalfByte(z1, p) if ok { a[j] = coeff j++ } if j >= len(a) { break } } return a } // sampleInBall samples a ringElement with coefficients in {−1, 0, 1}, and τ // non-zero coefficients. It is not constant-time. func sampleInBall(rho []byte, p parameters) ringElement { H := sha3.NewShake256() H.Write(rho) s := make([]byte, 8) H.Read(s) var c ringElement for i := 256 - p.τ; i < 256; i++ { j := make([]byte,...

113549, 2, 5}, crypto.SHA1: {1, 3, 14, 3, 2, 26}, // https://csrc.nist.gov/projects/computer-security-objects-register/algorithm-registration // // nistAlgorithms OBJECT IDENTIFIER ::= { joint-iso-ccitt(2) country(16) us(840) // organization(1) gov(101) csor(3) nistAlgorithm(4) } // // hashAlgs OBJECT IDENTIFIER ::= { nistAlgorithms 2 } // // id-sha256 OBJECT IDENTIFIER ::= { hashAlgs 1 } // id-sha384 OBJECT IDENTIFIER ::= { hashAlgs 2 } // id-sha512 OBJECT IDENTIFIER ::= { hashAlgs 3 } // id-sha224...