Author: kbknapp

This is a follow up from my previous post. In that post, I conjectured that turning on LTO (Link Time Optimization) and increasing the optimization levels would increase the binary size. My thinking was that the optimizer would more aggressively inline the code since function calls add performance overhead, but after speaking with a few individuals about this I realized I might be wrong (which wouldn't be the first time by a long shot :) ). Some may say this is common sense, but when coming from higher level languages it's not always obvious. Like many things, Rust gives you full control over your code, and lets you pick which parts you care about. Do you care about raw speed, or binary size. In this post we'll talk about how…

Preface: This post is somewhat hard to write, because it contains code that I'm not proud of, it's messy...bloated...it's real. I'm exposing something, in a project that I'm proud of, that isn't great. Sometimes this is hard and painful. But I'm also a firm believer that this is how we grow. I think what I've learned while going through this experience will make me better in the future. Maybe someone else can learn something from me and become better too. It's common practice in the U.S. to make a new years resolution at the start of every calendar year. Top of many people's list is to lose some unwanted weight. For 2018, [crayon-5c70742faa1b6974537080-i/]  is starting to lose some weight too! Recently, @razrfalcon released a new tool to the Rust community…