aboutsummaryrefslogtreecommitdiff
path: root/nitrokey-sys/libnitrokey-v3.4.1/libnitrokey/device.h
diff options
context:
space:
mode:
authorDaniel Mueller <deso@posteo.net>2018-12-17 18:31:42 -0800
committerDaniel Mueller <deso@posteo.net>2018-12-17 18:31:42 -0800
commit97accf1ddd79bb69dfb74742a0518c40830657e4 (patch)
tree2e808cd031e70084f2ae7bce704bd7cab4956b5c /nitrokey-sys/libnitrokey-v3.4.1/libnitrokey/device.h
parent953717e1648359baa8196ae32e01313b82f2561e (diff)
downloadnitrocli-97accf1ddd79bb69dfb74742a0518c40830657e4.tar.gz
nitrocli-97accf1ddd79bb69dfb74742a0518c40830657e4.tar.bz2
Make code conforming to rustfmt's expectations
An automated code formatter can help tremendously in reducing the amount of cognitive energy wasted on thinking about the "best" formatting of code as well as the number of nitpicks reviews typically get -- the format is machine checked (and enforced) and there is usually little to no discussion about the validity. To reach the goal of having such automated enforcement, we want to run the rustfmt tool as part of the CI pipeline. With rustfmt having reached 1.0 recently, the believe is that by now the formatting is reasonably stable and usable for this purpose. In that light, this change formats the code using rustfmt and prepares for such an automated style check.
Diffstat (limited to 'nitrokey-sys/libnitrokey-v3.4.1/libnitrokey/device.h')
0 files changed, 0 insertions, 0 deletions