| context 'performance' do | |
| before do | |
| require 'benchmark' | |
| @posts = [] | |
| @users = [] | |
| 8.times do |n| | |
| user = Factory.create(:user) | |
| @users << user | |
| aspect = user.aspects.create(:name => 'people') | |
| connect_users(@user, @aspect0, user, aspect) |
I recently started a new project using rspec's newer (and soon to be default) expect syntax, and encountered this error:
expect(5).to == 5
ArgumentError: The expect syntax does not support operator matchers, so you must pass a matcher to `#to`
"Why'd they take out operator matches? I've grown quite accustomed to them!", I thought. Digging around, the source of this change started in pull request 119 citing issue 138 as one of the root causes. Here's what's actually happening:
| bind-key C-b send-prefix | |
| bind-key C-o rotate-window | |
| bind-key C-z suspend-client | |
| bind-key Space next-layout | |
| bind-key ! break-pane | |
| bind-key " split-window | |
| bind-key # list-buffers | |
| bind-key $ command-prompt -I #S "rename-session '%%'" | |
| bind-key % split-window -h | |
| bind-key & confirm-before -p "kill-window #W? (y/n)" kill-window |