labofsahil/github-event-dataset-2012 huggingface dataset:
Okay, seems like I underestimated _how_ broken `isSafe` currently is (or, well, was), but this compiles, and won't with the changes folded in:

```d
import std.traits;

alias void function() @safe SafeFn;
static assert(isSafe!(SafeFn.init));
alias void function() @trusted TrustedFn;
static assert(isSafe!(TrustedFn.init));
alias void delegate() @safe SafeDg;
static assert(isSafe!(SafeDg.init));
alias void delegate() @trusted TrustedDg;
static assert(isSafe!(TrustedDg.init));
```

I just grepped through my sources, and apparently I have actually written code which uses `isSafe` in template constraints (and `RefRange` seems to use it as well, btw) – I must have been incredibly lucky, because I can't recall noticing any problems with it. Yes, my code probably works out of coincidence given the bugs in the `isSafe` implementation, but it is supposed to work given the Phobos docs.

Changing the two instance of `isSafe` to `isSafelyCallable` would be trivial, of course, but I'm not sure if it's worth introducing a breaking change, given that – and this is where the argument detailed in the forum thread comes in, regardless of whether the proposal is accepted or not – it doesn't really make sense to use `isSafe` and `isTrusted` in just about any situation. And if somebody really needs that information, they can always use `FunctionAttributes` directly.

By the way, `SetFunctionAttributes` actually distinguishes between `@safe` and `@trusted` for consistency, but this, i.e. pretty printing function types, is about the only use case for `isSafe`/`isTrusted' I can think of. And if you are doing that, chances are you are using all of the other `FunctionAttributes` anyway.
Maybe shorten

> In the interim, std.string.xformat and std.string.xsformat have been temporarily added, and they include the new implementation for those who need it immediately.

to

> In the interim, the new implementations are available as `std.string.xformat` and `std.string.xsformat` […]

or something like that? The original seems a bit long-winded to me. Also, stylistically, I'm not sure about using »we« in the change log.

In general, I agree that the focus should lie on the change in behavior to `format`/`sformat`, not the (possible) addition of the prefixes ones.
I think its OK now, because when you get a 404, Varnish or something else like a proxy server may think that 404's are for all users the same. When you return a 403(access denied), then the proxy server knows it could be different for other people.
SpriteDefinition, forgot it :D
we usually don't have an empty line after if/while/for I think
let me know if you'd like me to change crouching,gazing, et al. back to their original variable names for easier comparison
ok, pas super bon en francais :)
mais je m'applique

Le 30 octobre 2012 09:04, Renaud LITTOLFF <notifications@github.com> a
écrit :

> In fr/Contents/chapter4.md:
>
> > @@ -33,6 +33,143 @@ TODO: https://github.com/mageekguy/atoum/wiki/Modifier-l'espace-de-nom-par-d%C3%
> >
> >  TODO: https://github.com/mageekguy/atoum/wiki/Utiliser-atoum-avec-eZ-publish
> >
> > -## utilisation avec sf2
> > +## utilisation avec symfony 2
> > +
> > +Vous avez la possibilité d'utiliser atoum sur un projet symfony 2 avec
> > +[JediAtoumBundle](https://github.com/FlorianLB/JediAtoumBundle) mais vous avez aussi la possibilité d'utiliser
> > +atoum avec seulement [le fichier PHAR](http://downloads.atoum.org/nightly/mageekguy.atoum.phar
> ).
> > +
> > +### Etape 1 : Initialisation de votre classe de test
> > +
> > +Par défaut, nous avons le bundle Acme/DemoBundle. Ajouter le dossier Acme/DemoBundle/Entity et créer le
>
> Utilise plutôt l'impératif que l'infinitif. On dirait une recette de
> cuisine :)
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/marmotz/atoum-s-documentation/pull/10/files#r1975929>.
>
>
Leave it in or take it out.
I think you might be doing this in the wrong place.

You're only running local commands when we process an incoming record for our GUID — e.g., if someone sends us a command. Shouldn't we run local commands every time we sync?
I didn't want to expose this value in the global interface/contract for the cookbook, I thought it would confuse the documentation for the larger use case of standing up chef-servers.  It shouldn't be that big a deal as the list of repos is pretty static at this point.
This should check for plone.app.referenceablebehavior instead of plone.dexterity...because it is possible to have plone.dexterity but not plone.app.referenceablebehavior.
I added this back in, as it was not necessary to remove it.
This will unfortunately turn into a game of cat and mouse. There's quite a few more operating system in the redhat family than what's provided here, and we will be perpetually catching up against changes in facter.

Facter should be authoritative and the issue should be patched in facter, and there is a patch pending (http://projects.puppetlabs.com/issues/15792). In this case as a work around is just to distribute a custom version of osfamily via plugin sync if updating factor is an issue.

It's also possible to work around in puppet manifest site.pp to change $::osfamily to RedHat for Amazon linux to fix this globally.
At @andrewdavey's suggestion
Please invoke `hide!` in this generator so we hide it as well from `rails g`
`receiverVersion - otherObjectVersion < UINT32_MAX / 2` should be equivalent. This way you don't need to check for `receiverVersion == otherObjectVersion` explicitly.
We actually need to ensure that calculations return a map entry for each member of their input cohort. So the ret.put line needs to be outside of the inner loop.
It should already allow this. I haven't played around with refinery in a while, but I remember it allowing you to paste and save the formatting, if desired.
I've tried this and other browsers give unreliable results for $('html').scrollTop
well S (and mu) should be computed from as much available data as is there, so in case you have both lhs and rhs use both and lhs!=rhs use them otherwise just lhs :-)
if `tag_data` is really just a list of tag names, call it `tag_names`
wow triple underscores - never saw that before. Solaris rox.
Hi, Gary!
How about to simplify this into:
```
public void setObjectNames(ObjectName... objectNames) {
		Assert.notNull(ObjectUtils.isEmpty(objectNames), "'objectNames' must contain at least one ObjectName");
		this.objectNames = objectNames;
	}
```
And remove `setObjectName` at all?
I don't think we should get into the internals here. Elsewhere the doc refers generally to a generic MessageListener container.

i.e. a container for a MessageListener.
Please revert the change in this line.
Not really applicable for this. Would break the usual styling etc... Rather keep it as is.
yeap.
var levelMap = simpleStage();
`window.console.debug(...)` :-)
OK, you have it. :-)
The previous punctuation was meant to break the code up in a very specific way. The changes change the intent.
Style wise, I might consider moving this onto one line so that it looks more balanced:

```
if date.is_a? String then date = DateTime.parse(date) end
```

However, this might indicate that we need to look at something more generic for building query parameters rather than calling CGI::escape directly.

I know this method was originally added to get an accounting integration working duringr a hack day experiment, so it was more about getting the thing working than building out the Gem API properly.
should output something useful to the user?
This doesn't work on OS X. Could you add a switch (`[[ "x$(uname)" == "xDarwin"]]` and use `pmset`? Or is this left as an exercise for the user?

Example output:

```
$ pmset -g batt
Currently drawing from 'AC Power'
 -InternalBattery-0     59%; charging; 1:28 remaining
```
I think it makes sense to make this method public so that clients can get entities from API (with "include_entities=true") and call this method to auto-link.
Avoid protected fields just as you would public ones.
Our Azure APIs (storage, service bus, and now management) are pretty consistent in that they do not do this.  It would be a breaking change for us to modify our old APIs to be encapsulating options in classes.  If we do it just for management API, it will look different/weird.  We think our Python API is slightly more discoverable with parameters vs classes.

In Python you can keep compatibility while adding default parameters, that's not a problem.  Other languages may have limitations that prevent them from doing that?
This the link you really should be using -
http://developer.blackberry.com/native/beta/download/

So I recommend calling it
```
[BlackBerry 10 Native SDK] (http://developer.blackberry.com/native/beta/download/)
```

Core Native is cool but after they reach the link you provided they still need to find "Core" and click again.
I will also be fine with calling it

[BlackBerry 10 Core Native SDK] (http://developer.blackberry.com/native/beta/download/) 

but I think both mentioning "BlackBerry 10" is important since Playbook also has a NDK
**Error:** Variable "raw_url" is not in valid camel caps format
Its supposed to, thats the final implementation of StreamWriter nut just inherited so it can implement IStreamWriter
is there any reason that we want to explicitly name the table?
Isn't this autoconfigured?
let's make this be a "!" instead of a "=== false".  I assume this was just to avoid having to add the getter to the imap dude.  This is idiomatically weird, and if someone added another account type and left it off, we'd still probably do the wrong thing, so I don't think it's getting us anything.
why using ``form_widget`` ? This does not display the errors and the labels
вот тут совсем непонятно, что передается
Sure. Hopefully we can also address which formatter to use for 
Arquillian, in that JIRA ticket. I've seen these two formatters floating 
around in pull requests and forum discussions.
I am not sure about description and return description.
No - it should be defined like:
```php
AND u.user_type NOT IN (" . USER_INACTIVE . "," . USER_IGNORE . ")";
```
Another MODs can add new user types, you cannot ignore this fact.
Not sure whether this should be final. as it is just an ordinary setter
Do you also want to double check the action is correct: invokeRequest.action !== 'bb.action.PUSH' throw an error
`Cordova` variable must be really replaced with the following code:

```javascript
/* The new cordova-js project uses window.cordova property to define Cordova
 * API, but old PhoneGap API is still in use by Cordova iOS 1.5 which is
 * using window.Cordova property.
 */
var cordova = window.cordova || window.Cordova;

cordova.exec(...
```
Again, please fix comment formatting.