labofsahil/github-event-dataset-2012 huggingface dataset:
The description was copy/pasted from copy and it seems I forgot to rename some occurrences of 'copy'.
The difference between copyInto and copy is that the OutputRange is passed by reference for copyInto.

This solves the std.digest issue related to copy ( http://forum.dlang.org/post/503A3CB8.607@erdani.org )

Merging this functionality into copy is imho the better option, but it could break some corner cases:
```d

struct Value
{
    int a;
    void put(int x)
    {
        a += x;
    }
}

auto val = Value(10);
auto res = copy([1,2,3], val);
auto res2 = copy([4,5], val);
assert(val.a == 10); //With proposed changes: 25
assert(res.a == 16); //With proposed changes: 25
assert(res2.a == 19); //With proposed changes: 25
```
The documentation for copy doesn't describe how it works with OutputRanges so we can probably make that change?

Another question is whether we want to change the behaviour for arrays as well and pass arrays by reference, so their ```.length``` would get updated?
Now followings have same meaning.
- `trieCache.clear()` and `.clear(trieCache)`, but the name 'clear' is scheduled for deprecation.
- `trieCache.destroy()` and `.destroy(trieCache)`, but you think it is confusable...?
- `trieCache = null`

What is better?
Multiworld support thanks to Silthus/DeathControl@a946ed307a157df27eabf1a4098bbdc2d0698294
Perhaps

    var batching = (req.param("batch") === "true" || req.param === true)
this is wrong. You should not support any class here as you require extending DTO
Can you mention that all of the service/parameter prefixes have changed from `doctrine.odm.mongodb.` to `doctrine_mongodb.odm.`?
yeah, I meant indexes. Obviously not a big deal either way, but I thought it might make the API more consistent to remove String altogether.
I like `request.domain` because then user doesn't have to configure one more thing. Maybe we could set `Refinery::Inquiries.inquiry_from_email` to nil by default and then use something like this:

```ruby
def from(request)
  Refinery::Inquiries.inquiry_from_email || "no-reply@#{request.domain}"
end

....

mail :from => "\"#{Refinery::Core.site_name}\" <#{from(request)}>"
```
A builder would separate the concerns, and make the code more readable.

```php
$container->get('serializer.builder')->enableGroups(array('Foo'))->setVersion('1.0')->addExclusionStrategy($foo)->build();
```

Right now, the serializer is container scoped, and when you retrieve it, and start adding strategies, you don't really know what internal state it is in. We would also need to add methods to reset strategies because it is stateful at the moment. The more methods we add the more complicated this gets.
Please conform to the style guide.

Single quotes, space between `)` and `{`, ...
On my Arch box, `/usr/include/bits/temrios.h`, which is included by `/usr/include/termios.h`, has `#define NCCS 32`.
I think the pyramid 1.4 compat fix should go in the ``get_model`` method, and instead of try/except the exception we could just return  ``model_class.context`` if ``model_class`` is an ``i18n.I18NModel`` instance.
rename getResources to getRegister
Well, we talked about many things including copying CCF as is and changing the related code, but I think its you who suggested that wrapping might have JMX implications since the instance that is publicly exposed is not going to be the same instance as available from the AC. I actually have a wrapped version, so may be you can elaborate on what did you mean by JMX implications.

Also, understand that its not CCF that creates an issue, its the SessionProxy, so what I need to intercept is createSession call and wrap the Proxy into some type a wrapper to make sure that createConsumer call is intercepted since this is the one that creates a problem. Anyway either way it would not be hard to do since the current CCF actually does exactly that.

I just wanted to make sure that the required functionality is  there and it works as expected and it does.
Wow, you might want to switch places here, right? I mean put assertion up top
That I can't tell (can't remember), but it doesn't matter I guess. . . Its the difference between fully initializing EvaluationContext with the root object OR initializing it without root object while passing it with every evaluation. I think both code was initially written when we were all also learning SpEL API so there is a bit of an inconsistency there, but I hope you can see that its doing the same thing
Good point. Top should be added.
I'm checking for null here... maybe a bit defensive, but I kind of prefer it this way here.
Yeah -- should not be generalized to "factories", but specifically to "closures" -- and likely any  instantiable object, just to be on the safe side.
`Grespective` &rarr; `respective`
The intention was to wrap time.sleep in case we needed to switch back to real mode.
However I changed all the code to do smart waiting (i.e. not just sleep but also check for ACTIVE status when waiting for an instance) so this isn't necessary anymore allowing me to remove the nap function.
C'est une typo.
Can we remove the requires on Hashie then? (and from the Gemfile, if it's in there?)
reset va zetoe markazi yanichi?:)
manzooretun ineke linkesho bezaram
It'd be better to rename `str` to `url`
nit: 2 spaces soft tabs for HTML files too :)
`actionsObjects` is just needed if you use clipboard actions.
1.8.2 should have this.
Before accessing any struct properties on an object, it should be verified that it is non-`nil`.
@madebydna You are right. We should probably not to include heavy javascript in `application.js`. But if `application.js` contains very simple codes, so I don't mind to put it there because we have to introduce another file to let people to find where the codes located. There is `require_self` in asset pipeline if you are really care about including order, so it means in asset pipeline this way is always bad. But either way is good for me.

> How about we call the site file community.js rather than site.js.

I would prefer `site.js`, so that we keep this convention and consistant in other projects as well.
Suggest we add a test and assertion for every possible attribute - if we had had such a test before we would have caught this.
These brackets needed to be in there
is there a webplatform change for this that hasn't been merged?
Yea, this is done to simplify things for the user. This way they can copy over the 3 items to this folder and not have to worry about setting up the proper folder structure.
must be master
I'm not sure what ramifications this has on other parts of the code.  Can you explain your reasoning why you set this to "NULL"?  Would it not be better to simply set it to a blank string?
break out into own test and test corner cases of pagination
Indeed dynamic is not var. I was just focusing on the readability.. However I agree for Com things is one of the use cases for var. Pls send me a mail, when you commit some changes because I don't get any notification, when new changes happens
You should use `htmlize(comment.body)` here so that it is properly formatted and sanitized.
"... Each *type is* ... *the* initializer ..."