nma.arvydas.silanskas
2019-7-23 18:47:33

what are the technical difficulties of implementing generic methods in typed rackets?


boeyen
2019-7-23 19:50:38

@boeyen has joined the channel


samth
2019-7-23 20:47:05

There are two issues. First, what the type checking rules should be. Second, how to analyze the macros that implement generic method definitions and do the type checking.


samth
2019-7-23 20:47:26

Some progress has been made in working on supporting struct properties, see the recent RFC.


jaz
2019-7-23 21:54:21

When you’re making changes to the reference in development, what’s the best way to preview those changes (rendered, I mean)?


mflatt
2019-7-23 21:56:03

I use raco setup -l scribblings/reference


jaz
2019-7-23 21:58:20

does this entail first installing the racket-doc package using raco link?


jaz
2019-7-23 21:59:59

just by itself, it tells me that the collection isn’t found


mflatt
2019-7-23 22:02:41

Yes, that’s assuming that you have racket-doc installed and are editing in the installed copy. (Don’t use raco link. Use the raco pkg family of commands.) What kind of Racket installation do you have?


jaz
2019-7-23 22:04:16

I’m using an in-place build on a cloned repo. The reference is part of the repo, so if I just do a normal package install of racket-doc, won’t it pull it from the network?


mflatt
2019-7-23 22:04:45

You just typed make? Or make PKGS=<something>?


jaz
2019-7-23 22:05:57

just make (from racket/src/build) but when I tried `make PKGS="racket-doc", it didn’t render any docs


mflatt
2019-7-23 22:07:26

If you just typed make, then you got the default package installation of main-distribution, which includes racket-doc. A raco pkg show racket-doc should show that you have the package installed as a link to “pkgs/racket-doc” within your Git clone. You should edit documentation there, and raco setup -l scribblings/reference will rebuild from there.


mflatt
2019-7-23 22:07:53

This works because make sets up a catalog that maps the subset of packages included in the the main racket repo to the directories containing those packages.


jaz
2019-7-23 22:08:27
jaz@jons-mbp:~/src/97jaz/racket/racket/src/build (hash-ref-key)$ ../../bin/raco pkg show racket-doc
Installation-wide:
 [none]
User-specific for installation "7.4.0.3":
 [none]

mflatt
2019-7-23 22:09:35

Oh, I mean make at the top level of the Git clone, not in “build”


jaz
2019-7-23 22:10:35

Should I not be using build, in general?


mflatt
2019-7-23 22:11:49

They cooperate, but you want all the extra things that make at the top does.


jaz
2019-7-23 22:11:59

ok, thanks!