hunter.t.joz
2018-6-26 15:34:35

Okay, thanks.


obradford
2018-6-26 16:54:37

@obradford has joined the channel


steve
2018-6-26 19:01:07

To my joy I just (re)discovered the ARMV6 snapshot build on https://www.cs.utah.edu/plt/snapshots/, which is great as I’d been having problems compiling from source+built-packages in recent 6.x builds on Raspbian (Package manager SSL probs). I’m wondering if there’s a chance that with the official 7 release there could be packages for Raspbian explicitly made available, as the current RaspPi package actually in Raspbian is 6.7?


notjack
2018-6-26 19:10:47

I seemed to finally get things working yesterday, let me know if you see any issues


abmclin
2018-6-26 19:34:33

I don’t think flat-contract-with-explanation’s printed representation is working as expected based on current contract documenation and experience with other contracts. (flat-contract-with-explanation (λ (v) v)) will print #<flat-contract: temp1> I’d have expected it to print ???

(flat-contract-with-explanation string?) will print #<flat-contract: string?> instead of string?

(flat-contract-with-explanation #:name 'a-name string?) prints as #<flat-contract: a-name> instead of a-name

Is this a genuine issue? At the very least I think it’s inconsistent with the other contracts’ printed representations.


shu--hung
2018-6-26 21:23:53

@abmclin I think the explanation shows up when the contract is violated > (contract (flat-contract-with-explanation #:name 'a-name string?) 5 'server 'client) . . /head/racket/collects/racket/contract/private/blame.rkt:347:0: ...om an unsaved editor:28:2: broke its own contract promised: string? produced: 5 in: a-name contract from: server blaming: server (assuming the contract is correct)


shu--hung
2018-6-26 21:24:33

or:


shu--hung
2018-6-26 21:25:39
(module m racket
  (provide
   (contract-out [f (flat-contract-with-explanation #:name 'a-name string?)]))
  (define f 0))

(require 'm)

shu--hung
2018-6-26 21:26:13

temp1 seems weird to me too, but the problem is probably somewhere else


gfb
2018-6-26 22:56:23

gfb
2018-6-26 22:58:04

@gfb commented on @gfb’s file https://racket.slack.com/files/U6XN7R4JZ/FBEP77YAZ/-.txt\|Untitled: Ok, new to slack, meant to introduce that by asking if ellipsis patterns in match are known to be problematic, or if filing some of these as issues is worthwhile. Earlier today I filed an issue where something similar gave an expansion-time error.


gfb
2018-6-27 00:51:15

@lexi.lambda just commented on the GitHub issue, and it appears that repeated use of an identifier that’s in some ellipsified pattern has undefined behaviour.