...value, it gets costly (because they're a lot more expensive to copy than a raw pointer). If you never do it, then there's no point in using a shared pointer in the first place. Copy the shared pointer when a new function or object needs to share ownership of the pointee. ...

...ecause that won't affect the assembly that you just NGen'd. (Since it has raw machine code without referencing String.Equals). I assume that if that were to actually happen, the security update would clear the NGen store. Note that this attribute is only useful in the .NET Framework assemblies. Yo...

...t's really a matter of preference. I prefer to do all crypto operations on raw binary and only ever convert to hex/base64 for transmission or storage. – Scott Arciszewski Dec 18 '15 at 18:56 ...

....\n", pid); }' trace processes calling sleep bpftrace -e 'tracepoint:raw_syscalls:sys_enter { @[comm] = count(); }' count syscalls by process name --End--bpftrace bpf

....\n", pid); }' trace processes calling sleep bpftrace -e 'tracepoint:raw_syscalls:sys_enter { @[comm] = count(); }' count syscalls by process name --End--bpftrace bpf

....\n", pid); }' trace processes calling sleep bpftrace -e 'tracepoint:raw_syscalls:sys_enter { @[comm] = count(); }' count syscalls by process name --End--bpftrace bpf

....\n", pid); }' trace processes calling sleep bpftrace -e 'tracepoint:raw_syscalls:sys_enter { @[comm] = count(); }' count syscalls by process name --End--bpftrace bpf

....\n", pid); }' trace processes calling sleep bpftrace -e 'tracepoint:raw_syscalls:sys_enter { @[comm] = count(); }' count syscalls by process name --End--bpftrace bpf

....\n", pid); }' trace processes calling sleep bpftrace -e 'tracepoint:raw_syscalls:sys_enter { @[comm] = count(); }' count syscalls by process name --End--bpftrace bpf

....\n", pid); }' trace processes calling sleep bpftrace -e 'tracepoint:raw_syscalls:sys_enter { @[comm] = count(); }' count syscalls by process name --End--bpftrace bpf