- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 46 for errorea (0.17 sec)
-
src/bytes/buffer_test.go
if err != nil { t.Errorf("read error: %v", err) } if n != 0 { t.Errorf("wrong count; got %d want 0", n) } } func TestUnreadByte(t *testing.T) { b := new(Buffer) // check at EOF if err := b.UnreadByte(); err == nil { t.Fatal("UnreadByte at EOF: got no error") } if _, err := b.ReadByte(); err == nil { t.Fatal("ReadByte at EOF: got no error") }
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Fri Apr 26 13:31:36 GMT 2024 - 18.6K bytes - Viewed (0) -
src/archive/zip/reader_test.go
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Wed Mar 27 18:23:49 GMT 2024 - 55.3K bytes - Viewed (0) -
src/cmd/api/api_test.go
defer func() { if x := recover(); x != nil { t.Errorf("expected no panic; recovered %v", x) } }() testenv.MustHaveGoBuild(t) for _, context := range contexts { w := NewWalker(context, "testdata/src/issue64958") pkg, err := w.importFrom("p", "", 0) if err != nil { t.Errorf("expected no error importing; got %T", err) } w.export(pkg) } }
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Thu Jan 04 17:31:12 GMT 2024 - 7.1K bytes - Viewed (0) -
src/cmd/cgo/doc.go
This program will not compile, but cgo can use the presence or absence of an error message on a given line to deduce the information it needs. The program is syntactically valid regardless of whether each name is a type or an ordinary identifier, so there will be no syntax errors that might stop parsing early. An error on not-declared:1 indicates that foo is undeclared.
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Sun Mar 31 09:02:45 GMT 2024 - 42.1K bytes - Viewed (0) -
doc/go1.17_spec.html
</p> <h2 id="Errors">Errors</h2> <p> The predeclared type <code>error</code> is defined as </p> <pre> type error interface { Error() string } </pre> <p> It is the conventional interface for representing an error condition, with the nil value representing no error. For instance, a function to read data from a file might be defined:
HTML - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Thu Apr 11 20:22:45 GMT 2024 - 211.6K bytes - Viewed (0) -
.github/ISSUE_TEMPLATE/01-pkgsite.yml
validations: required: false - type: textarea id: what-did-you-do attributes: label: "What did you do?" description: "If possible, provide a recipe for reproducing the error. Starting with a Private/Incognito tab/window may help rule out problematic browser extensions." validations: required: true - type: textarea id: actual-behavior attributes:
Others - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Thu Jan 04 23:31:17 GMT 2024 - 1.4K bytes - Viewed (0) -
src/archive/tar/common.go
var ( ErrHeader = errors.New("archive/tar: invalid tar header") ErrWriteTooLong = errors.New("archive/tar: write too long") ErrFieldTooLong = errors.New("archive/tar: header field too long") ErrWriteAfterClose = errors.New("archive/tar: write after close") ErrInsecurePath = errors.New("archive/tar: insecure file path") errMissData = errors.New("archive/tar: sparse file references non-existent data")
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Fri Mar 15 16:01:50 GMT 2024 - 24.7K bytes - Viewed (2) -
src/cmd/asm/internal/asm/testdata/riscv64error.s
MOVF $1, X5 // ERROR "unsupported constant load" MOVBU X5, (X6) // ERROR "unsupported unsigned store" MOVHU X5, (X6) // ERROR "unsupported unsigned store" MOVWU X5, (X6) // ERROR "unsupported unsigned store" MOVF F0, F1, F2 // ERROR "illegal MOV instruction" MOVD F0, F1, F2 // ERROR "illegal MOV instruction" MOV X10, X11, X12 // ERROR "illegal MOV instruction"
Others - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Sun Apr 07 03:32:27 GMT 2024 - 2.8K bytes - Viewed (0) -
.github/ISSUE_TEMPLATE/11-language-change.yml
validations: required: true - type: textarea id: error-handling-proposal attributes: label: Does this affect error handling? description: If so, how does this differ from previous error handling proposals? placeholder: | Yes or No If yes, 1.how does this differ from previous error handling proposals? validations: required: true
Others - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Wed Nov 22 20:49:24 GMT 2023 - 4.7K bytes - Viewed (0) -
doc/next/6-stdlib/99-minor/net/63116.md
The [DNSError] type now wraps errors caused by timeouts or cancellation. For example, `errors.Is(someDNSErr, context.DeadlineExceedeed)`
Plain Text - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Wed Apr 24 13:37:36 GMT 2024 - 198 bytes - Viewed (0)