The Chelsea Murders
The Chelsea Murders (known in the USA as Murder Games) is a thriller by Lionel Davidson. The book won the Crime Writers' Association's Gold Dagger Award.
 First edition | |
| Author | Lionel Davidson |
|---|---|
| Cover artist | D.G. Rossetti "The Blessed Damozel", 1878 |
| Country | United Kingdom |
| Language | English |
| Genre | Thriller |
| Publisher | Jonathan Cape |
Publication date | 1978 |
| Media type | Print (Hardcover & Paperback) |
| Pages | 237 pp |
| ISBN | 0-14-005136-8 |
| OCLC | 59018354 |
Plot summary
Someone is killing residents of the hip bohemian London neighborhood of Chelsea, home to literary giants of the past like Virginia Woolf. What thread connects them in someone's mad mind? The only clue is a fragment of film, which accidentally caught images of the murderer, dressed in an outlandish costume and mask.
Television adaptation
An adaptation of the novel was 1981 directed from Derek Bennett as a Television film and was released on DVD in March 2010.[1]
gollark: As well as having special casing for stuff, it often is just pointlessly hostile to abstracting anything:- lol no generics- you literally cannot define a well-typed `min`/`max` function (like Lua has). Unless you do something weird like... implement an interface for that on all the builtin number types, and I don't know if it would let you do that.- no map/filter/reduce stuff- `if err != nil { return err }`- the recommended way to map over an array in parallel, if I remember right, is to run a goroutine for every element which does whatever task you want then adds the result to a shared "output" array, and use a WaitGroup thingy to wait for all the goroutines. This is a lot of boilerplate.
gollark: It also does have the whole "anything which implements the right functions implements an interface" thing, which seems very horrible to me as a random change somewhere could cause compile errors with no good explanation.
gollark: - `make`/`new` are basically magic- `range` is magic too - what it does depends on the number of return values you use, or something. Also, IIRC user-defined types can't implement it- Generics are available for all of, what, three builtin types? Maps, slices and channels, if I remember right.- `select` also only works with the built-in channels- Constants: they can only be something like four types, and what even is `iota` doing- The multiple return values can't be used as tuples or anything. You can, as far as I'm aware, only return two (or, well, more than one) things at once, or bind two returns to two variables, nothing else.- no operator overloading- it *kind of* has exceptions (panic/recover), presumably because they realized not having any would be very annoying, but they're not very usable- whether reading from a channel is blocking also depends how many return values you use because of course
gollark: What, you mean no it doesn't have weird special cases everywhere?
gollark: It pretends to be "simple", but it isn't because there are bizarre special cases everywhere to make stuff appear to work.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.