sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: youtube-dl
Issue: Indiancine.ma
Labels: site-support-request

<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->


## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2019.05.20. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Make sure that all provided video/audio/playlist URLs (if any) are alive and playable in a browser.
- Make sure that site you are requesting is not dedicated to copyright infringement, see https://yt-dl.org/copyright-infringement. youtube-dl does not support such sites. In order for site support request to be accepted all provided example URLs should not violate any copyrights.
- Search the bugtracker for similar site support requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm reporting a new site support request
- [x] I've verified that I'm running youtube-dl version **2019.05.20**
- [x] I've checked that all provided URLs are alive and playable in a browser
- [x] I've checked that none of provided URLs violate any copyrights
- [x] I've searched the bugtracker for similar site support requests including closed ones


## Example URLs

- Single video: https://indiancine.ma/BKLU/player/
- Playlist: https://indiancine.ma/grid/year/list==ashish:Movies_with_Video

## Description

No login needed, file plays directly in browser.
Repository: opencv
Issue: Inf/Nan in cvProjectpoints2
Labels: category: calib3d

- Can we have `inf/nan` issue in [`cvProjectPoints2Internal`](https://github.com/opencv/opencv/blob/db900af8c7a849539aff3941c2a788c190bb317b/modules/calib3d/src/calibration.cpp#L786-L787)?

- How we are informing the user about clipping not visible (in the camera plane) points?

From https://github.com/opencv/opencv/pull/14411#issuecomment-498224542
/cc @alalek 

See also https://answers.opencv.org/question/20138/projectpoints-fails-with-points-behind-the-camera/
Repository: go
Issue: cmd/vet: document interaction with test sources
Labels: Documentation,NeedsFix,Analysis

<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.12.5 linux/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/cosmin/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/cosmin/go:/home/cosmin/dev/git"
GOPROXY=""
GORACE=""
GOROOT="/usr/lib/go-1.12.5"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go-1.12.5/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="<project dir in  go path>/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build217071151=/tmp/go-build -gno-record-gcc-switches"

</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

Run `go vet something_test.go`

### What did you expect to see?

Successful execution

### What did you see instead?

```isomething_test.go: undefined: MyModel```

even if `MyModel` is defined and `go test` executes successfully.

It may be a regression of https://github.com/golang/go/issues/26797
Repository: go
Issue: cmd/cgo: warning: built-in function ‘free’ declared as non-function
Labels: help wanted,NeedsFix

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.11.6 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/yath/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/yath/go"
GOPROXY="https://proxy.golang.org,direct"
GORACE=""
GOROOT="/tmp/go"
GOTMPDIR=""
GOTOOLDIR="/tmp/go/pkg/tool/linux_amd64"
GCCGO="/usr/bin/gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build688375222=/tmp/go-build -gno-record-gcc-switches"
GOROOT/bin/go version: go version devel +98100c56da Mon Jun 3 01:37:58 2019 +0000 linux/amd64
GOROOT/bin/go tool compile -V: compile version devel +98100c56da Mon Jun 3 01:37:58 2019 +0000
uname -sr: Linux 5.1.5
Distributor ID:	Debian
Description:	Debian GNU/Linux 10 (buster)
Release:	10
Codename:	buster
/lib/x86_64-linux-gnu/libc.so.6: GNU C Library (Debian GLIBC 2.28-10) stable release version 2.28.
lldb --version: lldb version 6.0.1
gdb --version: GNU gdb (Debian 8.2.1-2) 8.2.1
</pre></details>

### What did you do?

`go run` the following program that is using `C.free` as a value. (In actual code, it’s passed to a `foo_set_free_fun(void (*)(void *))`.) The warning is not emit when calling `C.free()`, nor is it when e.g. printing the address of `C.getenv`.

```go
package main

// #include <stdlib.h>
import "C"
import "fmt"

func main() {
        fmt.Printf("%#v\n", C.free)
}
```


### What did you expect to see?

<pre>
(unsafe.Pointer)(0x402030)
</pre>

### What did you see instead?

<pre>
# command-line-arguments
cgo-generated-wrappers:1:13: warning: built-in function ‘free’ declared as non-function [-Wbuiltin-declaration-mismatch]
(unsafe.Pointer)(0x402030)
</pre>
Repository: pytorch
Issue: Title of docs page includes "PyTorch master documentation" even for non-master branches.
Labels: module: docs,triaged

E.g. go to https://pytorch.org/docs/stable/ and look at the HTML title of the page. It is `PyTorch documentation — PyTorch master documentation`
Repository: godot
Issue: Curve2D is not very clear
Labels: enhancement,documentation

The documentation of Curve2D is not very clear (class_curve2d.rst)

The `add_point` method method doesn't specify that the `Vector2 in` and `Vector2 out` (the control points / tangent), are local coordinates ( `(0,0)` is the point position in first parameter).

Furthermore, in `get_closest_offset`, we speak about a "local space", wich seems to be the space implicitly defined with the coordinates of the points (I mean we don't set explicitly what is the unit used). This precision isn't written anywhere, it would be great if it's the case.

Please confirm that I'm correct, and if someone can write better than me, it would be great :)
Repository: terminal
Issue: Add a test to cover closing two sibling panes (near) simultaneously
Labels: Area-UserInterface,Product-Terminal,Issue-Task,Area-CodeHealth

* [ ] Dependent upon #1042.

I'm adding code in #825 to try and make sure that when a pane is closed nearly synchronously with a sibling, it'll close properly. However, manually testing this is _really_ hard, so I'm filing a follow-up task to make sure that's implemented correctly.

I'll need the test framework stuff I'm working on in 1042 to land first though, so this can be done in a unittest.
Repository: flutter
Issue: [Material] Create a MaterialTapTargetSize for slider and consume in Range Slider
Labels: c: new feature,framework,f: material design,c: proposal,P3,team-design,triaged-design

https://api.flutter.dev/flutter/material/MaterialTapTargetSize.html
Repository: flutter
Issue: [iOS 13] new fullscreen stack type route transition
Labels: c: new feature,framework,a: fidelity,f: cupertino,f: routes,P1,team-design,triaged-design

While the old slide style transition still exists:

![Kapture 2019-06-03 at 14 31 13](https://user-images.githubusercontent.com/156888/58835987-482aba00-860c-11e9-9d5e-f1abf669cee9.gif)

There's an entirely new style now:

![Kapture 2019-06-03 at 14 32 28](https://user-images.githubusercontent.com/156888/58836042-714b4a80-860c-11e9-9c2b-6614917abcc1.gif)
Repository: go
Issue: proposal: x/crypto/blake2s: add New(size, key)
Labels: Proposal,Proposal-Crypto

<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version 1.12.2

</pre>

### Does this issue reproduce with the latest release?

yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env GOHOSTARCH="amd64" GOHOSTOS="linux"



</pre></details>

### What did you do?


I want to be able to export newDigest for blake2s. blake2s.New128 and blake2s.New256 are great, but I want to interface with one function that can take hash size as an input (like blake2b.New)




### What did you expect to see?

I want something like blake2b.New, but for blake2s. One way to make that easy is just export blake2s.newDigest


### What did you see instead?

function isn't available for export in the package
Repository: rust
Issue: Unconditional_recursion lint not triggered in procedural macro
Labels: A-lints,A-macros,T-compiler,C-bug

Hi,
I ma working with edition 2018 and I tried this piece of code with 1.37 nightly, 1.35 and 1.32 (random pick) with the same result.
Sorry if the point of my issue is at the end but I belive that the code is much more clear than me.

The code is:

lib.rs:
```rust
extern crate proc_macro;

use proc_macro::TokenStream;

#[proc_macro_derive(TestMacro)]
pub fn derive_answer_fn(input: TokenStream) -> TokenStream {
    let name = input.into_iter().nth(1).unwrap();

    format!(
        r#"
        pub trait A {{
            fn f() -> Self;
        }}

        #[deny(unconditional_recursion)]
        impl A for {0} {{
            fn f() -> Self {{

            let a = 0;
                <{0} as A>::f()
            }}
        }}"#, name.to_string()
    ).parse().unwrap()
}
```

test.rs:
```rust
use m::TestMacro;

#[derive(TestMacro)]
struct Struct;

fn main() {
    Struct::f();
}
```

I thought my test code would behave like:
```rust
struct Struct;

pub trait A {
    fn f() -> Self;
}

#[deny(unconditional_recursion)]
impl A for Struct {
    fn f() -> Self {
        <Struct as A>::f()
    }
}

fn main() {
    Struct::f();
}
```
giving this error:
```
error: function cannot return without recursing
```

instead compiles and (obviously)
```
thread 'main' has overflowed its stack
fatal runtime error: stack overflow
```

Am I doing something wrong? 
When does the linter check my code? 
Is this a normal behavoir?
Repository: pytorch
Issue: Undefined symbols for architecture x86_64: "testing::internal::UntypedFunctionMockerBase::UntypedInvokeWith(void const*)" on Mac OS X
Labels: module: build,module: internals,low priority,triaged,module: macos

I get the following linker failure attempting to build on Mac:

```
[590/2104] Linking CXX executable bin/c10_either_test
FAILED: bin/c10_either_test 
: && /usr/local/opt/ccache/libexec/g++  -Wno-deprecated -fvisibility-inlines-hidden -Wno-deprecated-declarations -Xpreprocessor -fopenmp -I/usr/local/include -DUSE_FBGEMM -O2 -fPIC -Wno-narrowing -Wall -Wextra -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wno-sign-compare -Wno-unused-parameter -Wno-unused-variable -Wno-unused-function -Wno-unused-result -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=deprecated-declarations -Wno-error=pedantic -Wno-error=redundant-decls -Wno-error=old-style-cast -Wno-invalid-partial-specialization -Wno-typedef-redefinition -Wno-unknown-warning-option -Wno-unused-private-field -Wno-inconsistent-missing-override -Wno-aligned-allocation-unavailable -Wno-c++14-extensions -Wno-constexpr-not-const -Wno-missing-braces -Qunused-arguments -fcolor-diagnostics -faligned-new -fno-math-errno -fno-trapping-math -Wno-unused-private-field -Wno-missing-braces -Wno-c++14-extensions -Wno-constexpr-not-const -O2 -g -DNDEBUG -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk -mmacosx-version-min=10.9 -Wl,-search_paths_first -Wl,-headerpad_max_install_names -rdynamic c10/test/CMakeFiles/c10_either_test.dir/util/either_test.cpp.o  -o bin/c10_either_test  -Wl,-rpath,/Users/jamesreed/pytorch/build/lib lib/libc10.dylib lib/libgmock.a lib/libgtest.a lib/libgtest_main.a lib/libgtest.a && :
Undefined symbols for architecture x86_64:
  "testing::internal::UntypedFunctionMockerBase::UntypedInvokeWith(void const*)", referenced from:
      (anonymous namespace)::ClassWithDestructorCallback::~ClassWithDestructorCallback() in either_test.cpp.o
      (anonymous namespace)::OnlyMoveableClassWithDestructorCallback::~OnlyMoveableClassWithDestructorCallback() in either_test.cpp.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
[591/2104] Building CXX object c10/test/CMakeFiles/c10_logging_test.dir/util/logging_test.cpp.o
```

I've been told BUILD_BINARY=0 BUILD_TEST=0 gets around it. Trying that now, but seems like there's a root cause here to be diagnosed
Repository: TypeScript
Issue: You actually can get Infinity type if you're clever and other fun floating point oddities
Labels: Discussion

As explained in [#15135](https://github.com/microsoft/TypeScript/issues/15135) and [#15351](https://github.com/microsoft/TypeScript/issues/15351), the Typescript team doesn't intend to support NaN and Infinity literals, due to complexity. Explicitly typing something as Infinity or -Infinity gives the error:

```
'Infinity' refers to a value, but is being used as a type here.
```

As it turns out, you actually can get the Infinity type fairly easily. Just use a really large number that parses to infinity as your type, like 1e999. -1e999 gives you negative Infinity. Fortunately, I don't believe you can get NaN from just parsing a double precision literal other than NaN itself. 0/0 is the simplest way to get NaN, but that's 2 literals and a divide.

There are a number of other floating point literal peculiarities resulting from round-off as well. I fully expect the Typescript team to "won't fix" them:
```
type DoesntExtend = 1.000000000000001 extends 1 ? 'yes' : 'no' // Resolves to 'no'
type Extends      = 1.0000000000000001 extends 1 ? 'yes' : 'no' // Resolves to 'yes'
```

Here's another. 
```
type NegativeZero = -0 extends 0 ? 'yes' : 'no'; // Resolves to 'yes'
```
In this case, -0 and 0 are actually distinct numbers with different bit patterns. Both Chrome and Firefox dev consoles correctly echo -0 as -0 rather than 0. However, the IEEE-754 standard defines that 0 === -0, so I'm not surprised Typescript thinks they're the same type. The intent for this distinction is to convey the idea of limits as a numeric representation (not to mention floating point is sign-magnitude anyways, so why not embrace it). For example, 1/-Infinity and -8*0 both result in -0 rather than 0. For a type system, I'm not sure that you strictly need or want to maintain this distinction.

<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  Repro'd on playground

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**
Infinity, NaN
**Code**

```
type Illegal = Infinity; // Doesn't compile
type Inf = 1e999; // Resolves to Infinity
type NegativeInf = -1e999; // Resolves to -Infinity
```

**Expected behavior:**


**Actual behavior:**

**Playground Link:** <!-- A link to a TypeScript Playground "Share" link which demonstrates this behavior -->
[Here](https://www.typescriptlang.org/play/#src=type%20Foo%20%3D%200%3B%20%2F%2F%20Illegal%0D%0Atype%20Bar%20%3D%201e999%3B%20%2F%2F%20Resolves%20to%20Infinity%0D%0Atype%20Baz%20%3D%20-1e999%20%2F%2F%20Resolves%20to%20-Infinity%0D%0A)

**Related Issues:** <!-- Did you find other bugs that looked similar? -->
Repository: rust
Issue: `rustc` runs out of memory while trying to compile a large static (lazy_static!) HashMap
Labels: A-borrow-checker,T-compiler,I-compilemem,C-bug

```
    Blocking waiting for file lock on build directory
   Compiling crash v0.1.0 (/home/fred/Workspace/rtuts/crash)
error: Could not compile `crash`.

Caused by:
  process didn't exit successfully: `rustc --edition=2018 --crate-name crash src/main.rs --color always --crate-type bin --emit=dep-info,link -C debuginfo=2 -C metadata=71bdac3a949cee3b -C extra-filename=-71bdac3a949cee3b --out-dir /home/fred/Workspace/rtuts/crash/target/debug/deps -C incremental=/home/fred/Workspace/rtuts/crash/target/debug/incremental -L dependency=/home/fred/Workspace/rtuts/crash/target/debug/deps --extern lazy_static=/home/fred/Workspace/rtuts/crash/target/debug/deps/liblazy_static-7468e7fc38fb612c.rlib` (signal: 9, SIGKILL: kill)

shell returned 101

```

My machine has 48GB of memory, yet still can't compile the example project, which creates a static hash map at compile time.

I tried both nightly and stable, same thing.

The input source code is only 19M, only containing u32s and strings. This shouldn't happen, GCC could do this no problem.

![2019-06-04-161946_2554x1540_scrot](https://user-images.githubusercontent.com/838783/58863042-957a5a80-86e4-11e9-85a1-d2d5125cac7f.png)

# Project [crash.zip](https://github.com/rust-lang/rust/files/3251295/crash.zip)
Repository: go
Issue: os: could not iterate over named pipes on Windows
Labels: OS-Windows,NeedsInvestigation

<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.12.5 windows/amd64
</pre>

### Does this issue reproduce with the latest release?

yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\mars9\AppData\Local\go-build
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\Users\mars9\go
set GOPROXY=
set GORACE=
set GOROOT=C:\Go
set GOTMPDIR=
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set GCCGO=gccgo
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=C:\Users\mars9\AppData\Local\Temp\go-build413446826=/tmp/go-build -gno-record-gcc-switches
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->
I wanted to iterate over Windows' named pipes using `os` package:
```golang
	f, err := os.Open(`\\.\pipe`)
	if err != nil {
		log.Fatalf("Could not open pipe list: %s", err)
	}
	defer f.Close()
	stat, err := f.Stat()
	if err != nil {
		log.Fatalf("Could not get file stats: %s", err)
	}
	log.Printf("Is Directory: %t", stat.IsDir()) // output: false
	pipelist, err := f.Readdir(-1)
	if os.IsNotExist(err) {
		log.Print("Pipe list does not exist")
	} else if err != nil {
		log.Printf("Could not read pipe list: %s", err)
	}
	for _, pipe := range pipelist {
		log.Printf("Pipe found: %s", pipe.Name())
	}
```

### What did you expect to see?

The same result as in Python:

```python
for pipeName in os.listdir(r'\\.\pipe'):
    print("Pipe found: %s" % pipeName)
```
```
Pipe found: InitShutdown
Pipe found: lsass
Pipe found: ntsvcs
Pipe found: scerpc
...
```

### What did you see instead?

```
Is Directory: false
Pipe list does not exist
```
Repository: vue
Issue: Stringify Vue instance
Labels: discussion

### Version
2.6.10

### Reproduction link
[https://codesandbox.io/s/vue-stringify-instance-2h78n](https://codesandbox.io/s/vue-stringify-instance-2h78n)

### Steps to reproduce
Open the link, the error is reproduced right away as the code tries to serliaze the Vue instance.

### What is expected?
Being able to serlialize the Vue instance.

### What is actually happening?
Is not possible as the Vue prototype is missing the toJSON method.

---
The code is using `telejson` as the stringify library in order to remove circular references. Is the same utility used by Storybook 5 which will rise those errors in diferent scenarios, as for example when using the Action addon and passing as argument a Vue instance.

<!-- generated by vue-issues. DO NOT REMOVE -->
Repository: godot
Issue: Clicking F5 is causing many save request calls to the plugin
Labels: bug,topic:editor,confirmed,topic:plugin

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:**
3.1.1

**OS/device including version:**
Ubuntu 18.04, 64bit, gtx1060

**Issue description:**
I noticed that when scene has unsaved changes, clicking F5 on the keyboard will cause many `save_external_data` calls in the plugin. 
It can be a problem in scenario when saving the state of plugin takes a little longer (save operation take many times more time than in should). 
From my short investigation it probably is a problem related to how keyboard shortcuts are implemented in the editor. The place at which I was looking at, was `BaseButton._unhandled_input()` function (where stacktrace took me when I used a breakpoint, placed at the line with the `save_external_data` call on the engine site (`EditorData::save_editor_external_data()`)).


**Steps to reproduce:**
Simple way:
1. Download sample project
2. Run Godot from terminal window and open the sample project
3. Open 'SomeScene.tscn'
4. Move spatial somewhere and click F5
5. In terminal window observe multiple lines in a row starting with `SaveIssue: Plugin is saving external data`

Manual way:
1. Run Godot from console
2. Create new plugin
3. Put this script in the main script file of the plugin:
```
tool
extends EditorPlugin

func save_external_data() -> void:
	print("SaveIssue: Plugin is saving external data at msec time: ", OS.get_ticks_msec())
```
4.. Create new scene, put a Spatial inside, save it
5. Each time when you want to reproduce the problem, make local changes to the scene by moving spatial somewhere and click F5 on the keyboard, and take a look at terminal window (output inside editor is cleared at the moment of starting the sample)

**Minimal reproduction project:**
[PluginSaveIssue.zip](https://github.com/godotengine/godot/files/3252131/PluginSaveIssue.zip)
Repository: flutter
Issue: Expose the Google Maps Geometry Library in the maps plugin
Labels: c: new feature,p: maps,package,c: proposal,team-ecosystem,P3,triaged-ecosystem

## Use case

I need to calculate area occupied by a polygon on a Google map.
I understand that the maps plugin is WIP but it still would be a nice to have.
While I only currently need only one function it probably makes sense to add support for the entire library
https://developers.google.com/maps/documentation/javascript/reference/geometry#spherical.computeArea

## Proposal

Add support for the Google Maps Geometry Library as a part of Maps plugin or a separate one.