Manage state as in SAWScript

[david-christiansen]

SAWScript contains an ambient state that includes things like the currently-loaded Cryptol modules. In a prior iteration of this API, the intention was to abolish this implicit state and provide all information explicitly in each call. However, this made it more difficult to share code with SAWScript, and it was unclear that the extra expressive power was actually useful.

This should be disentangled.

The SAWScript state is maintained here:

argo/saw-remote-api/src/SAWServer.hs

Lines 62 to 63 in fc8ed96

	, _sawTopLevelRO :: TopLevelRO
	, _sawTopLevelRW :: TopLevelRW

The most important code to change is in the SAWServer.CryptolSetup module. It should be replaced by code that updates the implicit state rather than saving a Cryptol setup value into the environment. See e.g.

argo/saw-remote-api/src/SAWServer/CryptolSetup.hs

Lines 60 to 68 in fc8ed96

	cryptolSetupLoadFile :: CryptolSetupLoadFileParams -> Method SAWState OK
	cryptolSetupLoadFile (CryptolSetupLoadFileParams fileName) =
	cryptolSetupMethod $
	\cenv ->
	do sc <- biSharedContext . view sawBIC <$> getState
	let qual = Nothing -- TODO add field to params
	let importSpec = Nothing -- TODO add field to params
	cenv' <- liftIO $ CEnv.importModule sc cenv (Left fileName) qual importSpec
	return (cenv', OK)

.

[david-christiansen]

@atomb I think you made this happen late last year, right?