what conditions does the optimization improve performance? • can the decision be automatic? • Safety: under what conditions does the optimization preserve correctness? • maintain state semantics University 2020 Catalog of Optimizations 14 ??? Vasiliki Kalavri | Boston University 2020 15 Safety • Attribute availability: the set of attributes B reads from must be disjoint from the set of re-ordering with Eddy B A D C Eddy C D A B ??? Vasiliki Kalavri | Boston University 2020 18 Safety • attribute availability: the set of attributes B reads from must be disjoint from the set of attributes

Marshal(gopher) fmt.Println(string(asBytes)) // "{"full_name":"Gopher Cleveland","Age":40}" Tag Safety Problem What if you need to reference the content of a tag? Useful for MongoDB, ORMs, etc. Workaround initializers. Lets your initialization logic live inside its type definition. Drawbacks Loss of compile safety. Most use cases are too complex for this method. Go’s struct literal syntax is already pretty slick

this as the “raw web service”. You will then have neither native object orientation nor full type safety, since web services are neither object-oriented nor stateful. However, in this way, you can write similar typecasts, as the new style should use the correct type in most places, increasing the type safety in case of an error in the source code. To gloss over the platform differences, API client code should medium is set to the new value. Both increasing and decreasing the size is possible, and there are no safety checks, since VirtualBox does not make any assumptions about the medium contents. Resizing usually

this as the “raw web service”. You will then have neither native object orientation nor full type safety, since web services are neither object-oriented nor stateful. However, in this way, you can write similar typecasts, as the new style should use the correct type in most places, increasing the type safety in case of an error in the source code. To gloss over the platform differences, API client code should medium is set to the new value. Both increasing and decreasing the size is possible, and there are no safety checks, since VirtualBox does not make any assumptions about the medium contents. Resizing usually

this as the “raw web service”. You will then have neither native object orientation nor full type safety, since web services are neither object-oriented nor stateful. However, in this way, you can write similar typecasts, as the new style should use the correct type in most places, increasing the type safety in case of an error in the source code. To gloss over the platform differences, API client code should medium is set to the new value. Both increasing and decreasing the size is possible, and there are no safety checks, since VirtualBox does not make any assumptions about the medium contents. Resizing usually

this as the “raw web service”. You will then have neither native object orientation nor full type safety, since web services are neither object-oriented nor stateful. However, in this way, you can write similar typecasts, as the new style should use the correct type in most places, increasing the type safety in case of an error in the source code. To gloss over the platform differences, API client code should medium is set to the new value. Both increasing and decreasing the size is possible, and there are no safety checks, since VirtualBox does not make any assumptions about the medium contents. Resizing usually

this as the “raw web service”. You will then have neither native object orientation nor full type safety, since web services are neither object-oriented nor stateful. However, in this way, you can write similar typecasts, as the new style should use the correct type in most places, increasing the type safety in case of an error in the source code. To gloss over the platform differences, API client code should medium is set to the new value. Both increasing and decreasing the size is possible, and there are no safety checks, since VirtualBox does not make any assumptions about the medium contents. Resizing usually

this as the “raw web service”. You will then have neither native object orientation nor full type safety, since web services are neither object-oriented nor stateful. However, in this way, you can write similar typecasts, as the new style should use the correct type in most places, increasing the type safety in case of an error in the source code. To gloss over the platform differences, API client code should medium is set to the new value. Both increasing and decreasing the size is possible, and there are no safety checks, since VirtualBox does not make any assumptions about the medium contents. Resizing usually

this as the “raw web service”. You will then have neither native object orientation nor full type safety, since web services are neither object-oriented nor stateful. However, in this way, you can write similar typecasts, as the new style should use the correct type in most places, increasing the type safety in case of an error in the source code. To gloss over the platform differences, API client code should medium is set to the new value. Both increasing and decreasing the size is possible, and there are no safety checks, since VirtualBox does not make any assumptions about the medium contents. Resizing usually

this as the “raw web service”. You will then have neither native object orientation nor full type safety, since web services are neither object-oriented nor stateful. However, in this way, you can write similar typecasts, as the new style should use the correct type in most places, increasing the type safety in case of an error in the source code. To gloss over the platform differences, API client code should medium is set to the new value. Both increasing and decreasing the size is possible, and there are no safety checks, since VirtualBox does not make any assumptions about the medium contents. Resizing usually