resolve/instantiateの違い

(@v1.9) pkg> ?instantiate
  instantiate [-v|--verbose]
  instantiate [-v|--verbose] [-m|--manifest]
  instantiate [-v|--verbose] [-p|--project]

  Download all the dependencies for the current project at the version given by the project's manifest. If no manifest exists
  or the --project option is given, resolve and download the dependencies compatible with the project.

  After packages have been installed the project will be precompiled. For more information see pkg> ?precompile.

(@v1.9) pkg> ?resolve
  resolve

  Resolve the project i.e. run package resolution and update the Manifest. This is useful in case the dependencies of
  developed packages have changed causing the current Manifest to be out of sync.

(@v1.9) pkg> ?precompile
  precompile
  precompile pkgs...

  Precompile all or specified dependencies of the project in parallel. The startup.jl file is disabled during precompilation
  unless julia is started with --startup-file=yes.

  Errors will only throw when precompiling the top-level dependencies, given that not all manifest dependencies may be loaded
  by the top-level dependencies on the given system.

  This method is called automatically after any Pkg action that changes the manifest. Any packages that have previously
  errored during precompilation won't be retried in auto mode until they have changed. To disable automatic precompilation set
  the environment variable JULIA_PKG_PRECOMPILE_AUTO=0. To manually control the number of tasks used set the environment
  variable JULIA_NUM_PRECOMPILE_TASKS.

(@v1.9) pkg>