doudengjin8251
doudengjin8251
2013-10-28 23:07

Go bytes.Buffer是线程安全的吗?

已采纳

In the Go programming language, is bytes.Buffer thread-safe? AFAIK, its documentation does not mention thread safety.

  • 点赞
  • 写回答
  • 关注问题
  • 收藏
  • 复制链接分享
  • 邀请回答

3条回答

  • dongquepao8653 dongquepao8653 8年前

    No.

    The Go documentation follows a simple rule: If it is not explicitly stated that concurrent access to something is safe, it is not.

    点赞 评论 复制链接分享
  • dongzen5577 dongzen5577 5年前

    No - but you can easily wrap it in a thread safe struct!

    For simple things:

    type Buffer struct {
        b bytes.Buffer
        m sync.Mutex
    }
    func (b *Buffer) Read(p []byte) (n int, err error) {
        b.m.Lock()
        defer b.m.Unlock()
        return b.b.Read(p)
    }
    func (b *Buffer) Write(p []byte) (n int, err error) {
        b.m.Lock()
        defer b.m.Unlock()
        return b.b.Write(p)
    }
    func (b *Buffer) String() string {
        b.m.Lock()
        defer b.m.Unlock()
        return b.b.String()
    }
    

    ..and use it as usual var buf Buffer, etc.

    Want more of bytes.Buffer? Feel free to cherry pick:

    func (b *Buffer) Bytes() []byte {
        b.m.Lock()
        defer b.m.Unlock()
        return b.b.Bytes()
    }
    func (b *Buffer) Cap() int {
        b.m.Lock()
        defer b.m.Unlock()
        return b.b.Cap()
    }
    func (b *Buffer) Grow(n int) {
        b.m.Lock()
        defer b.m.Unlock()
        b.b.Grow(n)
    }
    func (b *Buffer) Len() int {
        b.m.Lock()
        defer b.m.Unlock()
        return b.b.Len()
    }
    func (b *Buffer) Next(n int) []byte {
        b.m.Lock()
        defer b.m.Unlock()
        return b.b.Next(n)
    }
    func (b *Buffer) ReadByte() (c byte, err error) {
        b.m.Lock()
        defer b.m.Unlock()
        return b.b.ReadByte()
    }
    func (b *Buffer) ReadBytes(delim byte) (line []byte, err error) {
        b.m.Lock()
        defer b.m.Unlock()
        return b.b.ReadBytes(delim)
    }
    func (b *Buffer) ReadFrom(r io.Reader) (n int64, err error) {
        b.m.Lock()
        defer b.m.Unlock()
        return b.b.ReadFrom(r)
    }
    func (b *Buffer) ReadRune() (r rune, size int, err error) {
        b.m.Lock()
        defer b.m.Unlock()
        return b.b.ReadRune()
    }
    func (b *Buffer) ReadString(delim byte) (line string, err error) {
        b.m.Lock()
        defer b.m.Unlock()
        return b.b.ReadString(delim)
    }
    func (b *Buffer) Reset() {
        b.m.Lock()
        defer b.m.Unlock()
        b.b.Reset()
    }
    func (b *Buffer) Truncate(n int) {
        b.m.Lock()
        defer b.m.Unlock()
        b.b.Truncate(n)
    }
    func (b *Buffer) UnreadByte() error {
        b.m.Lock()
        defer b.m.Unlock()
        return b.b.UnreadByte()
    }
    func (b *Buffer) UnreadRune() error {
        b.m.Lock()
        defer b.m.Unlock()
        return b.b.UnreadRune()
    }
    func (b *Buffer) WriteByte(c byte) error {
        b.m.Lock()
        defer b.m.Unlock()
        return b.b.WriteByte(c)
    }
    func (b *Buffer) WriteRune(r rune) (n int, err error) {
        b.m.Lock()
        defer b.m.Unlock()
        return b.b.WriteRune(r)
    }
    func (b *Buffer) WriteString(s string) (n int, err error) {
        b.m.Lock()
        defer b.m.Unlock()
        return b.b.WriteString(s)
    }
    func (b *Buffer) WriteTo(w io.Writer) (n int64, err error) {
        b.m.Lock()
        defer b.m.Unlock()
        return b.b.WriteTo(w)
    }
    
    点赞 评论 复制链接分享
  • dth42345 dth42345 7年前

    Use io.Pipe() function call which provide pair of connected objects (*PipeReader, *PipeWriter) for synchronous read/write. This could be done in parallel, and it's a thread-safe.

    点赞 评论 复制链接分享