Zulip Chat Archive

Stream: general

Topic: recreating `trace_state`


view this post on Zulip Jason Rute (Jan 27 2020 at 01:20):

A meta programming question: How would one recreate trace_state without using the built in formatter for the tactic_state type? I'm mostly interested in getting information found in trace_state, i.e. the context and targets for the other goals besides the current one, and not in the actual recreation of the trace_state. This code for example gets all the information for the current goal, but not for the other goals:

meta def trace_current_goal : tactic unit :=
do
 goal ← tactic.target,
 local_cxt ← tactic.local_context,
 local_cxt_types ← list.mmap tactic.infer_type local_cxt,
 let s := "Goal: " ++ (to_string goal) ++ "\nLocal Context: "++ (to_string local_cxt) ++ "\nLocal Context Types: " ++(to_string local_cxt_types),
 tractic.trace s,
return ()

view this post on Zulip Mario Carneiro (Jan 27 2020 at 04:20):

@Jason Rute tactic.target is a shorthand for (list.head <$> get_goals) >>= infer_type. If you want the other goals, call get_goals directly

view this post on Zulip Jason Rute (Jan 27 2020 at 13:20):

@Mario Carneiro how do I get the local_context for the other goals? What is tactic.local_context shorthand for? Is this documented anywhere?

view this post on Zulip Rob Lewis (Jan 27 2020 at 13:37):

local_context is implemented in c++, it's hard coded to give the context of the first goal. I'm not 100% sure this is robust, but you can typically do something like this (build whatever data structure you want instead of tracing).

example : true   x : , true :=
by do
  `[refine ⟨_, λ i, _⟩], -- give ourselves two goals with different local contexts
  trace_state,
  gs  get_goals,
  gs.mmap' $ λ g, set_goals [g] >> local_context >>= trace,
  set_goals gs,
  trace_state

Last updated: May 06 2021 at 22:13 UTC