existing global variable. This addresses both issues while preserving the "programming at scale" benefits of the 1.0 behavior: global variables have no spooky effect on the meaning of code that may be all processes other than process 1. As a result, adding 2 or more processes is required to gain benefits from parallel processing methods like pmap. Adding a single process is beneficial if you just wish and user code should only access them directly if this is stated to be the API. This has several benefits: • Package developers are freer to change the implementation without breaking user code. • Methods

existing global variable. This addresses both issues while preserving the "programming at scale" benefits of the 1.0 behavior: global variables have no spooky effect on the meaning of code that may be all processes other than process 1. As a result, adding 2 or more processes is required to gain benefits from parallel processing methods like pmap. Adding a single process is beneficial if you just wish and user code should only access them directly if this is stated to be the API. This has several benefits: • Package developers are freer to change the implementation without breaking user code. • Methods

existing global variable. This addresses both issues while preserving the "programming at scale" benefits of the 1.0 behavior: global variables have no spooky effect on the meaning of code that may be all processes other than process 1. As a result, adding 2 or more processes is required to gain benefits from parallel processing methods like pmap. Adding a single process is beneficial if you just wish and user code should only access them directly if this is stated to be the API. This has several benefits: • Package developers are freer to change the implementation without breaking user code. • Methods

existing global variable. This addresses both issues while preserving the "programming at scale" benefits of the 1.0 behavior: global variables have no spooky effect on the meaning of code that may be all processes other than process 1. As a result, adding 2 or more processes is required to gain benefits from parallel processing methods like pmap. Adding a single process is beneficial if you just wish and user code should only access them directly if this is stated to be the API. This has several benefits: • Package developers are freer to change the implementation without breaking user code. • Methods

existing global variable. This addresses both issues while preserving the "programming at scale" benefits of the 1.0 behavior: global variables have no spooky effect on the meaning of code that may be all processes other than process 1. As a result, adding 2 or more processes is required to gain benefits from parallel processing methods like pmap. Adding a single process is beneficial if you just wish and user code should only access them directly if this is stated to be the API. This has several benefits: • Package developers are freer to change the implementation without breaking user code. • Methods

existing global variable. This addresses both issues while preserving the "programming at scale" benefits of the 1.0 behavior: global variables have no spooky effect on the meaning of code that may be all processes other than process 1. As a result, adding 2 or more processes is required to gain benefits from parallel processing methods like pmap. Adding a single process is beneficial if you just wish and user code should only access them directly if this is stated to be the API. This has several benefits: • Package developers are freer to change the implementation without breaking user code. • Methods

existing global variable. This addresses both issues while preserving the "programming at scale" benefits of the 1.0 behavior: global variables have no spooky effect on the meaning of code that may be all processes other than process 1. As a result, adding 2 or more processes is required to gain benefits from parallel processing methods like pmap. Adding a single process is beneficial if you just wish and user code should only access them directly if this is stated to be the API. This has several benefits: • Package developers are freer to change the implementation without breaking user code. • Methods

existing global variable. This addresses both issues while preserving the "programming at scale" benefits of the 1.0 behavior: global variables have no spooky effect on the meaning of code that may be all processes other than process 1. As a result, adding 2 or more processes is required to gain benefits from parallel processing methods like pmap. Adding a single process is beneficial if you just wish and user code should only access them directly if this is stated to be the API. This has several benefits: • Package developers are freer to change the implementation without breaking user code. • Methods

existing global variable. This addresses both issues while preserving the "programming at scale" benefits of the 1.0 behavior: global variables have no spooky effect on the meaning of code that may be all processes other than process 1. As a result, adding 2 or more processes is required to gain benefits from parallel processing methods like pmap. Adding a single process is beneficial if you just wish and user code should only access them directly if this is stated to be the API. This has several benefits: • Package developers are freer to change the implementation without breaking user code. • Methods

existing global variable. This addresses both issues while preserving the "programming at scale" benefits of the 1.0 behavior: global variables have no spooky effect on the meaning of code that may be all processes other than process 1. As a result, adding 2 or more processes is required to gain benefits from parallel processing methods like pmap. Adding a single process is beneficial if you just wish and user code should only access them directly if this is stated to be the API. This has several benefits: • Package developers are freer to change the implementation without breaking user code. • Methods