This expression has type func but an expression was expected of type file about zshprof HOT 10 OPEN

That's weird, it seems to work for me.

I'm on ocaml 4.07.1, which are you on?

from zshprof.

Are you sure you're on the latest master? "Callgrind.ml", line 23, characters 17-22 doesn't quite seem to make sense.

from zshprof.

That's weird, it seems to work for me.

I'm on ocaml 4.07.1, which are you on?

I'm on ocaml 4.08.1 and ocamlfind 1.8.1 and opam 2.0.5.
Just now, I re-clone the latest source code, but got the same error. my steps are as follows(my computer is macbook pro, the system version is 10.15.1):

brew install ocaml
brew install opam
brew install qcachegrind
git clone https://github.com/raboof/zshprof.git
cd zshprof
opam init
eval `opam config env`
opam install ocamlfind
ocamlfind ocamlopt -linkpkg -thread -package str Callgrind.ml ZshXtrace.ml ZshXtraceToCallgrind.ml && ./a.out < /tmp/zshstart.70535.log  > zsh.callgrind

Then the error appeared

$ ocamlfind ocamlopt -linkpkg -thread -package str Callgrind.ml ZshXtrace.ml ZshXtraceToCallgrind.ml && ./a.out < /tmp/zshstart.70535.log  > zsh.callgrind
File "Callgrind.ml", line 23, characters 17-22:
Error: This expression has type func but an expression was expected of type
         file

I am not familiar with the module ocaml, so I don't quite understand how to deal with this error.

from zshprof.

Weird, with ocaml 4.08.1 and ocamlfind 1.8.1 (not using opam) I still can't reproduce the problem.

I must have looked in the wrong place before, "Callgrind.ml", line 23, characters 17-22 actually does make sense. I changed things around a bit to make them less ambiguous. Perhaps that solves something, or otherwise at least it should produce a better error message.

Could you give the updated master a try?

from zshprof.

Weird, with ocaml 4.08.1 and ocamlfind 1.8.1 (not using opam) I still can't reproduce the problem.

I must have looked in the wrong place before, "Callgrind.ml", line 23, characters 17-22 actually does make sense. I changed things around a bit to make them less ambiguous. Perhaps that solves something, or otherwise at least it should produce a better error message.

Could you give the updated master a try?

I updated the master, the new error is:

$ ocamlfind ocamlopt -linkpkg -thread -package str Callgrind.ml ZshXtrace.ml ZshXtraceToCallgrind.ml && ./a.out < /tmp/zshstart.70535.log  > zsh.callgrind
File "ZshXtraceToCallgrind.ml", line 14, characters 6-16:
Error: Unbound record field label depth

from zshprof.

Super weird, I wonder if you have some leftovers from a previous compilations hanging around.

I just now added a Makefile, could you make clean, verify there's no remaining intermediate files, and try again?

from zshprof.

Super weird, I wonder if you have some leftovers from a previous compilations hanging around.

I just now added a Makefile, could you make clean, verify there's no remaining intermediate files, and try again?

It doesn't seem to work

$ make clean
rm log2callgrind *.cmi *.cmx *.o || true
rm: cannot remove 'log2callgrind': No such file or directory
rm: cannot remove '*.cmi': No such file or directory
rm: cannot remove '*.cmx': No such file or directory
rm: cannot remove '*.o': No such file or director

$ make
ocamlfind ocamlopt -linkpkg -thread -package str Callgrind.ml ZshXtrace.ml ZshXtraceToCallgrind.ml -o log2callgrind
File "ZshXtraceToCallgrind.ml", line 14, characters 6-16:
Error: Unbound record field label depth
make: *** [log2callgrind] Error 2

from zshprof.

These 'cannot remove' lines are just warnings, so that's OK.

Can you show the output of ls?

from zshprof.

These 'cannot remove' lines are just warnings, so that's OK.

Can you show the output of ls?

Callgrind.ml Makefile README.md ZshXtrace.ml ZshXtraceToCallgrind.m

from zshprof.

OK, I'm stumped then: line 14 of ZshXtraceToCallgrind.ml does line.depth where line is a ZshXtrace.line, and in ZshXtrace.md the line record most definitely has a depth...

from zshprof.