Remove the Sigma (monotonous state) API.

Reminder of (some of) the reasons for removal:

- Despite the claim in sigma.mli, it does *not* prevent evar
  leaks, something like:

  fun env evd ->
  let (evd',ev) = new_evar env evd in
  (evd,ev)

  will typecheck even with Sigma-like type annotations (with a proof of
  reflexivity)

- The API stayed embryonic. Even typing functions were not ported to
  Sigma.

- Some unsafe combinators (Unsafe.tclEVARS) were replaced with slightly
  less unsafe ones (e.g. s_enter), but those ones were not marked unsafe
  at all (despite still being so).

- There was no good story for higher order functions manipulating evar
  maps. Without higher order, one can most of the time get away with
  reusing the same name for the updated evar map.

- Most of the code doing complex things with evar maps was using unsafe
  casts to sigma. This code should be fixed, but this is an orthogonal
  issue.

Of course, this was showing a nice and elegant use of GADTs, but the
cost/benefit ratio in practice did not seem good.

1 files changed, 1 insertions, 3 deletions

diff --git a/vernac/vernacentries.ml b/vernac/vernacentries.ml
index c6ec89c5e..1332a7052 100644
--- a/vernac/vernacentries.ml
+++ b/vernac/vernacentries.ml
@@ -31,7 +31,6 @@ open Redexpr
 open Lemmas
 open Misctypes
 open Locality
-open Sigma.Notations
 
 module NamedDecl = Context.Named.Declaration
 
@@ -1550,8 +1549,7 @@ let vernac_check_may_eval ?loc redexp glopt rc =
         let (sigma',r_interp) = Hook.get f_interp_redexp env sigma' r in
 	let redfun env evm c =
           let (redfun, _) = reduction_of_red_expr env r_interp in
-          let evm = Sigma.Unsafe.of_evar_map evm in
-          let Sigma (c, _, _) = redfun.Reductionops.e_redfun env evm c in
+          let (_, c) = redfun env evm c in
           c
         in
 	Feedback.msg_notice (print_eval redfun env sigma' rc j)