with Julia, one may need to compile, call the C code from Julia, then close the library, make an edit, recompile, and load in the new changes. One can either restart Julia or use the Libdl functions to JULIA_EDITOR The editor returned by InteractiveUtils.editor() and used in, e.g., InteractiveUtils.edit, referring to the command of the preferred editor, for instance vim. $JULIA_EDITOR takes precedence and to any files loaded in to the REPL with includet (but not with plain include); you can then edit the files and the changes take effect without restarting your julia session. A standard workflow

with Julia, one may need to compile, call the C code from Julia, then close the library, make an edit, recompile, and load in the new changes. One can either restart Julia or use the Libdl functions to JULIA_EDITOR The editor returned by InteractiveUtils.editor() and used in, e.g., InteractiveUtils.edit, referring to the command of the preferred editor, for instance vim. $JULIA_EDITOR takes precedence and to any files loaded in to the REPL with includet (but not with plain include); you can then edit the files and the changes take effect without restarting your julia session. A standard workflow

with Julia, one may need to compile, call the C code from Julia, then close the library, make an edit, recompile, and load in the new changes. One can either restart Julia or use the Libdl functions to JULIA_EDITOR The editor returned by InteractiveUtils.editor() and used in, e.g., InteractiveUtils.edit, referring to the command of the preferred editor, for instance vim. $JULIA_EDITOR takes precedence it again. The key in the above is that your code is encapsulated in a module. That allows you to edit struct definitions and remove methods, without restarting Julia. 479CHAPTER 36. WORKFLOW TIPS 480

with Julia, one may need to compile, call the C code from Julia, then close the library, make an edit, recompile, and load in the new changes. One can either restart Julia or use the Libdl functions to JULIA_EDITOR The editor returned by InteractiveUtils.editor() and used in, e.g., InteractiveUtils.edit, referring to the command of the preferred editor, for instance vim. $JULIA_EDITOR takes precedence it again. The key in the above is that your code is encapsulated in a module. That allows you to edit struct definitions and remove methods, without restarting Julia. 479CHAPTER 36. WORKFLOW TIPS 480

with Julia, one may need to compile, call the C code from Julia, then close the library, make an edit, recompile, and load in the new changes. One can either restart Julia or use the Libdl functions to JULIA_EDITOR The editor returned by InteractiveUtils.editor() and used in, e.g., InteractiveUtils.edit, referring to the command of the preferred editor, for instance vim. $JULIA_EDITOR takes precedence it again. The key in the above is that your code is encapsulated in a module. That allows you to edit struct definitions and remove methods, without restarting Julia. 479CHAPTER 36. WORKFLOW TIPS 480

with Julia, one may need to compile, call the C code from Julia, then close the library, make an edit, recompile, and load in the new changes. One can either restart Julia or use the Libdl functions to JULIA_EDITOR The editor returned by InteractiveUtils.editor() and used in, e.g., InteractiveUtils.edit, referring to the command of the preferred editor, for instance vim. $JULIA_EDITOR takes precedence it again. The key in the above is that your code is encapsulated in a module. That allows you to edit struct definitions and remove methods, without restarting Julia. 490CHAPTER 36. WORKFLOW TIPS 491

with Julia, one may need to compile, call the C code from Julia, then close the library, make an edit, recompile, and load in the new changes. One can either restart Julia or use the Libdl functions to JULIA_EDITOR The editor returned by InteractiveUtils.editor() and used in, e.g., InteractiveUtils.edit, referring to the command of the preferred editor, for instance vim. $JULIA_EDITOR takes precedence it again. The key in the above is that your code is encapsulated in a module. That allows you to edit struct definitions and remove methods, without restarting Julia. 491CHAPTER 36. WORKFLOW TIPS 492

with Julia, one may need to compile, call the C code from Julia, then close the library, make an edit, recompile, and load in the new changes. One can either restart Julia or use the Libdl functions to JULIA_EDITOR The editor returned by InteractiveUtils.editor() and used in, e.g., InteractiveUtils.edit, referring to the command of the preferred editor, for instance vim. $JULIA_EDITOR takes precedence it again. The key in the above is that your code is encapsulated in a module. That allows you to edit struct definitions and remove methods, without restarting Julia. 490CHAPTER 36. WORKFLOW TIPS 491

with Julia, one may need to compile, call the C code from Julia, then close the library, make an edit, recompile, and load in the new changes. One can either restart Julia or use the Libdl functions to JULIA_EDITOR The editor returned by InteractiveUtils.editor() and used in, e.g., InteractiveUtils.edit, referring to the command of the preferred editor, for instance vim. $JULIA_EDITOR takes precedence it again. The key in the above is that your code is encapsulated in a module. That allows you to edit struct definitions and remove methods, without restarting Julia. 490CHAPTER 36. WORKFLOW TIPS 491

with Julia, one may need to compile, call the C code from Julia, then close the library, make an edit, recompile, and load in the new changes. One can either restart Julia or use the Libdl functions to JULIA_EDITOR The editor returned by InteractiveUtils.editor() and used in, e.g., InteractiveUtils.edit, referring to the command of the preferred editor, for instance vim. $JULIA_EDITOR takes precedence it again. The key in the above is that your code is encapsulated in a module. That allows you to edit struct definitions and remove methods, without restarting Julia. 490CHAPTER 36. WORKFLOW TIPS 491