- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 11 for Hancic (0.15 sec)
-
src/bytes/buffer_test.go
} } type panicReader struct{ panic bool } func (r panicReader) Read(p []byte) (int, error) { if r.panic { panic("oops") } return 0, io.EOF } // Make sure that an empty Buffer remains empty when // it is "grown" before a Read that panics func TestReadFromPanicReader(t *testing.T) { // First verify non-panic behaviour var buf Buffer
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) -
doc/go1.17_spec.html
At that point, the program is terminated and the error condition is reported, including the value of the argument to <code>panic</code>. This termination sequence is called <i>panicking</i>. </p> <pre> panic(42) panic("unreachable") panic(Error("cannot parse")) </pre> <p> The <code>recover</code> function allows a program to manage behavior of a panicking goroutine.
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) -
src/archive/zip/reader_test.go
b, err := hex.DecodeString(s) if err != nil { panic(err) } return b } func returnBigZipBytes() (r io.ReaderAt, size int64) { b := biggestZipBytes() for i := 0; i < 2; i++ { r, err := NewReader(bytes.NewReader(b), int64(len(b))) if err != nil { panic(err) } f, err := r.File[0].Open() if err != nil { panic(err) } b, err = io.ReadAll(f)
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/cgo/doc.go
uintptr_t _cgo_wait_runtime_init_done(void) { return 0; } void _cgo_release_context(uintptr_t ctxt) { } char* _cgo_topofstack(void) { return (char*)0; } void _cgo_allocate(void *a, int c) { } void _cgo_panic(void *a, int c) { } void _cgo_reginit(void) { } The extra functions here are stubs to satisfy the references in the C code generated for gcc. The build process links this stub, along with
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/godebug.md
The [GODEBUG History](#history) gives the exact defaults for each Go toolchain version. For example, Go 1.21 introduces the `panicnil` setting, controlling whether `panic(nil)` is allowed; it defaults to `panicnil=0`, making `panic(nil)` a run-time error. Using `panicnil=1` restores the behavior of Go 1.20 and earlier. When compiling a work module or workspace that declares
Plain Text - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Tue Apr 16 17:29:58 GMT 2024 - 13.5K bytes - Viewed (0) -
src/bytes/example_test.go
n, err := b.Read(rdbuf) if err != nil { panic(err) } fmt.Println(n) fmt.Println(b.String()) fmt.Println(string(rdbuf)) // Output: // 1 // bcde // a } func ExampleBuffer_ReadByte() { var b bytes.Buffer b.Grow(64) b.Write([]byte("abcde")) c, err := b.ReadByte() if err != nil { panic(err) } fmt.Println(c) fmt.Println(b.String())
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Mon Mar 04 15:54:40 GMT 2024 - 15K bytes - Viewed (1) -
src/builtin/builtin.go
func close(c chan<- Type) // The panic built-in function stops normal execution of the current // goroutine. When a function F calls panic, normal execution of F stops // immediately. Any functions whose execution was deferred by F are run in // the usual way, and then F returns to its caller. To the caller G, the // invocation of F then behaves like a call to panic, terminating G's
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Thu Apr 11 20:22:45 GMT 2024 - 12.7K bytes - Viewed (0) -
doc/go_spec.html
At that point, the program is terminated and the error condition is reported, including the value of the argument to <code>panic</code>. This termination sequence is called <i>panicking</i>. </p> <pre> panic(42) panic("unreachable") panic(Error("cannot parse")) </pre> <p> The <code>recover</code> function allows a program to manage behavior of a panicking goroutine.
HTML - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Thu May 02 22:43:51 GMT 2024 - 279.6K bytes - Viewed (0) -
src/cmd/api/main_test.go
} func (w *Walker) emitf(format string, args ...any) { f := strings.Join(w.scope, ", ") + ", " + fmt.Sprintf(format, args...) if strings.Contains(f, "\n") { panic("feature contains newlines: " + f) } if _, dup := w.features[f]; dup { panic("duplicate feature inserted: " + f) } w.features[f] = true if verbose { log.Printf("feature: %s", f) } }
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Tue Apr 09 20:48:51 GMT 2024 - 31.4K bytes - Viewed (0) -
doc/go_mem.html
If <code>list</code> pointed to a cyclic list, then the original program would never access <code>*p</code> or <code>*q</code>, but the rewritten program would. (Moving `*p` ahead would be safe if the compiler can prove `*p` will not panic; moving `*q` ahead would also require the compiler proving that no other goroutine can access `*q`.) </p> <p> Not introducing data races also means not assuming that called functions
HTML - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Mon Mar 04 15:54:42 GMT 2024 - 26.6K bytes - Viewed (0)