Îõ³h$»e      Safe-InferreduNone0splint¿Getting settings is not instantaneous. Since settings are usually reused between modules, it makes sense to cache them. However each module can potentially customize its settings using the  OPTIONS_GHCÙ pragma. This variable is used as a cache of settings keyed on the command line options. splintÉEven though we cache settings based on command line options, we only want to load settings one at a time. Practically this is to work around a bug in GHC. But aside from that, loading settings calls withArgsÁ and doing that simultaneously in separate threads is dubious. /https://gitlab.haskell.org/ghc/ghc/issues/18261  NoneW       %splint-1.0.2.0-BqXB0NB3CUSBDZiUcdqoRhSplint.RemoteDataSplint.SettingsSplint RemoteDataNotAskedLoadingFailureSuccess$fEqRemoteData$fShowRemoteDataSettingscache semaphore withTMVarloadpluginaction ideaToWarnMsg ideaToMsgDocparse