From 9ee5fd3698cd0dce437b6a6de8774f60ad352489 Mon Sep 17 00:00:00 2001 From: Artem Date: Mon, 30 Jul 2018 21:44:05 +0300 Subject: [PATCH] Break the C FFI notes to their respective lines for readability --- iguana/exchanges/mm2.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/iguana/exchanges/mm2.md b/iguana/exchanges/mm2.md index 00c530742..718209486 100644 --- a/iguana/exchanges/mm2.md +++ b/iguana/exchanges/mm2.md @@ -91,12 +91,12 @@ Let's list the good things that should come out of the gradual rewrite: The plan so far is to by default use the C functions as the atomic units of rewrite. Rust FFI allows us to swap any C function with a similar Rust function. -Porting on this level we -a) reuse the function-level modularity of the C language; -b) preserve the code meta-data (Git history will show a nice diff between the C and Rust functions, we'll be able to easily investigate the evolution of the code back to its roots); -c) avoid the complexity and slow-downs associated with adding RPC/networking layers or drawing new lines of abstraction; +Porting on this level we +a) reuse the function-level modularity of the C language; +b) preserve the code meta-data (Git history will show a nice diff between the C and Rust functions, we'll be able to easily investigate the evolution of the code back to its roots); +c) avoid the complexity and slow-downs associated with adding RPC/networking layers or drawing new lines of abstraction; d) have a good indicator of the porting progress (how many functions were ported, how many remains). Focusing on the function call chains that are a common part of a failure/crash or touch on the new functionality will allow us to leverage the [Pareto principle](https://en.wikipedia.org/wiki/Pareto_principle), -advancing on 80% of desired Value (stability, functionality) with 20% of effort. \ No newline at end of file +advancing on 80% of desired Value (stability, functionality) with 20% of initial effort. \ No newline at end of file