maddy/internal/msgpipeline
fox.cpp 305fdddf24
Use context.Context all over the place
It is useful to define background tasks lifetimes more precisely,
especially involving timeouts and other cancellation methods.

On top of that, several tracing facilities are context-based (e.g.
runtime/trace), so it is possible to use them now.
2019-12-13 17:31:35 +03:00
..
bench_test.go Move most code from the repo root into subdirectories 2019-12-06 01:35:12 +03:00
bodynonatomic_test.go Move most code from the repo root into subdirectories 2019-12-06 01:35:12 +03:00
check_runner.go Use context.Context all over the place 2019-12-13 17:31:35 +03:00
check_test.go Move most code from the repo root into subdirectories 2019-12-06 01:35:12 +03:00
config.go Move most code from the repo root into subdirectories 2019-12-06 01:35:12 +03:00
config_test.go Move most code from the repo root into subdirectories 2019-12-06 01:35:12 +03:00
dmarc_test.go Use context.Context all over the place 2019-12-13 17:31:35 +03:00
modifier_test.go Move most code from the repo root into subdirectories 2019-12-06 01:35:12 +03:00
msgid.go Move most code from the repo root into subdirectories 2019-12-06 01:35:12 +03:00
msgpipeline.go Use context.Context all over the place 2019-12-13 17:31:35 +03:00
msgpipeline_test.go Use context.Context all over the place 2019-12-13 17:31:35 +03:00
objname.go Move most code from the repo root into subdirectories 2019-12-06 01:35:12 +03:00
regress_test.go Move most code from the repo root into subdirectories 2019-12-06 01:35:12 +03:00