gvisor/pkg/flipcall
Michael Pratt 129018ab3d Consistent precondition formatting
Our "Preconditions:" blocks are very useful to determine the input invariants,
but they are bit inconsistent throughout the codebase, which makes them harder
to read (particularly cases with 5+ conditions in a single paragraph).

I've reformatted all of the cases to fit in simple rules:

1. Cases with a single condition are placed on a single line.
2. Cases with multiple conditions are placed in a bulleted list.

This format has been added to the style guide.

I've also mentioned "Postconditions:", though those are much less frequently
used, and all uses already match this style.

PiperOrigin-RevId: 327687465
2020-08-20 13:32:24 -07:00
..
BUILD Factor out flipcall mmap for internal use 2020-06-11 12:57:56 -07:00
ctrl_futex.go Don't log "p9.channel.service: flipcall connection shutdown". 2019-11-01 11:45:02 -07:00
flipcall.go Consistent precondition formatting 2020-08-20 13:32:24 -07:00
flipcall_example_test.go New sync package. 2020-01-09 22:02:24 -08:00
flipcall_test.go New sync package. 2020-01-09 22:02:24 -08:00
flipcall_unsafe.go New sync package. 2020-01-09 22:02:24 -08:00
futex_linux.go Don't log "p9.channel.service: flipcall connection shutdown". 2019-11-01 11:45:02 -07:00
io.go Flipcall refinements. 2019-07-31 12:56:04 -07:00
packet_window_allocator.go Specify a memory file in platform.New(). 2020-04-22 17:50:10 -07:00
packet_window_mmap.go Factor out flipcall mmap for internal use 2020-06-11 12:57:56 -07:00