Yuxin Wang
Yuxin Wang
**Describe the solution you'd like** Add disk io information per process, perhaps in `si.cpu()` or additional items in `si.diskIO()`. **Describe alternatives you've considered** Sorry I don't know much about windows...
> **Note** All credit goes to @abhinav This PR adds suggestions on formatting strings using `%q` over `%s`. Source: https://abhinavg.net/2021/12/29/fmt-errof-q/ by @abhinav Fixes #185
> **Note** All credit goes to @abhinav I learned this from one of @abhinav's amazing talks, and thought we could probably add this practice to this doc. Whenever formatting messages...
Chan et al. developed a SmartSum [1] algorithm that continuously releases private aggregate information, instead of simply releasing the noisy sum. (It is also available in Figure 12 of [2])....
This PR simply refactors the contract analyzer to prepare for further updates. Specifically, it (1) Defines a separate type for `[]Contract` such that it can be made to be exported...
This PR implements the fact export for manually-written and inferred function contracts. Specifically it enhances the `functioncontracts` sub-analyzer, which imports contracts from upstream packages, parses/infers the contracts for the local...
We already have support in NilAway for checking nilability in switch cases: ```go switch { case a == nil: case a.f == nil: // NilAway won't complain about a being...
NilAway currently does not track the side effects of validator functions: ```go //nilable(a) func validate(a *int) bool { return a != nil } //nilable(a) func foo(a *int) { if validate(a)...
Currently in NilAway we forbid sending to and receiving from nilable channels by creating corresponding consumers for them. However, in practice this will not result in panics. See the following...
For error-returning functions, NilAway will check if the error is properly checked, otherwise the pointer result will be treated as nilable. However, NilAway currently only supports checking the errors via...