Some files in the repository are missing newlines at the very end, as pointed out by @nrbrook in #1026

Classes/CocoaLumberjack.h was specifically mentioned, but there could be other files that are missing this as well.

While generating docs for the v5.2, I noticed our doc coverage dropped to 99% due to a forgotten doc here. and was wondering if it is a good idea to add a CI step to make sure any newly introduced code is properly documented

In several WWDC talks, Apple suggests to set the Input and Output files in all run script phases, so the build system can choose to skip a run script phase if nothing changed, improving incremental build time.

How could we improve R.swift‘s behavior here?

Note that I did not yet check if wildcards were allowed in the Input Files field. Or if we could somehow leverage the new File List field.

I want to send out the receipt to verify it by my own server.
I see remote receipt verification is available, but couldn't find the way to do it ?

https://github.com/libretro/blastem-libretro

Alternative Genesis Core with ARM support.

log.debug("A tagged log message", userInfo: Dev.dave | Tag.sensitive)

That's somehow will confuse the user who only advantages one kind of Tag.
Then I suggest appending one demo code as below for that scenario.
log.debug("A tagged log message", userInfo: Tag.sensitive.dictionary)

Can you generate API docs for MvvmCross code?
Like for example:

• Andorid API
• AutoFac API
• and many others (all libs from Microsoft, Google ...)

Why?

• API dosc boost developers productivity - You easy look through the code (without decompiling it).
• API docs

There does not seem to be any reference docs for recent versions of LayoutKit.

The current release is 9.0.0, but if I navigate to the documentation at http://layoutkit.org/code-documentation/, I'm sent to http://cocoadocs.org/docsets/LayoutKit/6.0.1/, which seems to be completely broken. There is but a single class listed DWUKVOLabel.

If I navigate to previous versions of the docs via the

@Zandor300 wrote in commit a6aa3da222ee9dc098ee2d2c35e5b406580e2189 to the current Podfile:

Might be smarter to reference it locally. That way the entire DeviceKit pod won't be stored twice in this repository. http://guides.cocoapods.org/using/the-podfile.html#using-the-files-from-a-folder-local-to-the-machine

pod 'DeviceKit', :path => '../'

I will try this out and provide a fix

Currently ResponseDetective prints <none> for bodies in the following situations:

1. when the body is empty, i.e. has 0 bytes;
2. and when the body cannot be deserialized, i.e. has an unsupported content-type.

The 2nd situation might be confusing as <none> might suggest that a request has an empty body.

The proposal is to improve handling of empty and non-deserializable bodies in the

Today we support the following platforms and architectures:

• iOS: ARMv7, ARMv7s and ARM64
• tvOS: ARM64
• watchOS: ARMv7k and ARM64_32
• macOS: x86_64

There has been some discussion about removing support (in .NET 5) for:

• iOS: ARMv7s
  • The ARMv7s architecture is not very much used, and provides very little benefit over ARMv7.
  • ARMv7 can be used anywhere ARMv7s is used. Gi

Some parts of image is missing

`let svgURL = URL(string: partsDetail.groupImageUrl)!
l