@royall please add email validations and the like to the expect package (or a separate package using expectations), I’ve been wanting to do that :p

ok, but first I have to find out what an expectation is

like a contract, but only for flat data and it gives you multiple error messages instead of just one

> (define positive-even (expect-all (expect-pred positive?) (expect-pred even?)))
> (expect! -7 positive-even)
multiple failures
  subject: -7
  fault: expected a different kind of value
   expected: positive?
   actual: -7
  fault: expected a different kind of value
   expected: even?
   actual: -7

We can catch these faults like exceptions for recovery and presentation to the user?

my racket error handling knowhow is minimal

Instead of expect! which throws an exception, you can use expectation-apply which just returns a list of faults

so you don’t have to call expect! and catch stuff

sounds good to me

(the expect package is one I made earlier this year and talked about at racketcon btw)

I wonder if anyone plans to chop those videos into something more manageable like the earlier racketcon vids

it’s in progress as far as I know

that’s great

the older racketcon vids are way more informative than other programming conference vids i’ve watched

that could be skewed by my php background

@leif did the chopping and editing last year, she’d know more about the progress this year

(hence the video language :p)

racket users need to become more aggressive at self promotion

if i can see a dozen tweets about another css framework, i want to see it for all this cool stuff

web stuff that’s more integrated with the non-racket world would be a good way of doing that